zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From phunt <...@git.apache.org>
Subject [GitHub] zookeeper issue #415: ZOOKEEPER-2939: Added last/min/max proposal size JMX b...
Date Sat, 16 Dec 2017 01:00:49 GMT
Github user phunt commented on the issue:

    > One approach (which this PR tries to follow) is to expose basic values which can
be sampled by a more sophisticated monitoring tool. Average, sliding window, etc. can be implemented
in there.
    That's fine, but I guess my thought was that sampling in this context will have very low
fidelity vs having the server calculate, the avg for example. Given the monitoring tool will
poll every 5 seconds or so (perhaps less frequently) the number of samples vs the number of
proposals could be very low. Not a reason not to do it, but I'm not sure you're really going
to get what you expect as an operator.


View raw message