GitHub user sjcorbett opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/283
Logging brooklyn-persister thread Jclouds messages in a separate file
When a server with persistence to an object store enabled manages lots of
entities the Jclouds log is overwhelmed by messages logged from the
brooklyn-persister thread (in one case logging at a rate of ~ half a million
lines every four minutes).
The appender added in this commit alleviates - a little! - this logging
overload.
Anecdotal measurements of the ratio between the persister log and jclouds
log sizes, with EmptySoftwareProcess entities:
```
0 entities: persister log 0.01 times size of jclouds log
1 entity: 0.36
5 entities: 1.13
10 entities: 1.75
50 entities: 8.6
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sjcorbett/incubator-brooklyn
log-persistence-thread
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/283.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #283
----
commit 652692455822e164c5baf0d3394e8c53c6f3eba3
Author: Sam Corbett <[email protected]>
Date: 2014-10-30T16:03:40Z
Logging brooklyn-persister thread Jclouds messages in a separate file
When a server with persistence to an object store enabled manages lots of
entities the Jclouds log is overwhelmed by messages logged from the
brooklyn-persister thread (in one case logging at a rate of ~ half a
million lines every four minutes).
The appender added in this commit alleviates - a little! - this logging
overload.
Anecdotal measurements of the ratio between the persister log and jclouds
log sizes, with EmptySoftwareProcess entities:
0 entities: persister log 0.01 times size of jclouds log
1 entity: 0.36
5 entities: ~1.13
10 entities: 1.75
50 entities: 8.6
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
