You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Edward Ribeiro (JIRA)" <ji...@apache.org> on 2013/01/09 06:08:12 UTC
[jira] [Updated] (ZOOKEEPER-1423) 4lw and jmx should expose the
size of the datadir/datalogdir
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Ribeiro updated ZOOKEEPER-1423:
--------------------------------------
Attachment: ZOOKEEPER-1423.patch
Hi folks,
I am sending a *first* version of a patch to address this issue. I am aware that it should probably be rewritten to be in sync with ZOOKEEPER-1346, but I hope you have time to evaluate it and see if it's okay to include in 3.5.
Any suggestion/correction is welcome.
Cheers,
E.
> 4lw and jmx should expose the size of the datadir/datalogdir
> ------------------------------------------------------------
>
> Key: ZOOKEEPER-1423
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1423
> Project: ZooKeeper
> Issue Type: Improvement
> Components: jmx
> Reporter: Patrick Hunt
> Labels: newbie
> Attachments: ZOOKEEPER-1423.patch
>
>
> There are no metrics currently available on the size of the datadir/datalogdir. These grow w/o bound unless the cleanup script is run. It would be good to expose these metrics through jmx/4lw such that monitoring can be done on the size. Would key ppl in on whether cleanup was actually running. In particular this could be monitored/alerted on by third party systems (nagios, ganglia and the like).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira