Hi Everyone,
Any chance the default setting for Hazelcast status updates in the log can be less frequent or disabled by default?
Every 30 seconds causes a lot of log pollution.
Thanks,
Dan
+1
Removing all the analytics garbage would also be good.
Regards,
Jason
···
On Thursday, October 9, 2014, Dan dan@dancocos.com wrote:
Hi Everyone,
Any chance the default setting for Hazelcast status updates in the log can be less frequent or disabled by default?
Every 30 seconds causes a lot of log pollution.
Thanks,
Dan
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
–
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049
agreed, possibly just send most or all of it to a different log file. In the mean time I mostly pipe cat and tail to grep -Ev ‘com.hazelcast.util.HealthMonitor|executor.q.async.size’
···
Timothy Harding
PeaceCorps Volunteer
Republic of Vanuatu
+678 5955137
On Fri, Oct 10, 2014 at 6:50 AM, Jason Pickering jason.p.pickering@gmail.com wrote:
+1
Removing all the analytics garbage would also be good.
Regards,
Jason
On Thursday, October 9, 2014, Dan dan@dancocos.com wrote:
Hi Everyone,
Any chance the default setting for Hazelcast status updates in the log can be less frequent or disabled by default?
Every 30 seconds causes a lot of log pollution.
Thanks,
Dan
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049
–
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
+1
I know at least one implementation where the bulk of what they are paying for relatively expensive ssd storage is mostly for analytics log storage. Growing considerably faster than the database. I think by default much of these should be DEBUG level rather than INFO.
···
On 9 October 2014 20:50, Jason Pickering jason.p.pickering@gmail.com wrote:
+1
Removing all the analytics garbage would also be good.
Regards,
Jason
On Thursday, October 9, 2014, Dan dan@dancocos.com wrote:
Hi Everyone,
Any chance the default setting for Hazelcast status updates in the log can be less frequent or disabled by default?
Every 30 seconds causes a lot of log pollution.
Thanks,
Dan
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049
–
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
Hi,
I have removed hazelcast info logging (in trunk and backported to 2.16) and
reduced analytics logging (trunk only) now.
regards,
Lars