[
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.7.patch
Good catch about the directory length, [~rgs]! My tests were exclusively on
Linux where it worked but it's definitely not safe to use it for directories,
as explained here
http://stackoverflow.com/questions/12432135/what-does-java-io-file-length-return-for-a-directory
, changed accordingly. Also, changed the import order, both changes in
ZOOKEEPER-1423.7.patch
> 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
> Affects Versions: 3.5.0
> Reporter: Patrick Hunt
> Assignee: Edward Ribeiro
> Labels: newbie
> Fix For: 3.5.1
>
> Attachments: ZOOKEEPER-1423.2.patch, ZOOKEEPER-1423.3.patch,
> ZOOKEEPER-1423.4.patch, ZOOKEEPER-1423.5.patch, ZOOKEEPER-1423.6.patch,
> ZOOKEEPER-1423.7.patch, 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 was sent by Atlassian JIRA
(v6.3.4#6332)
