[
https://issues.apache.org/jira/browse/ZOOKEEPER-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293511#comment-16293511
]
ASF GitHub Bot commented on ZOOKEEPER-2939:
-------------------------------------------
Github user phunt commented on the issue:
https://github.com/apache/zookeeper/pull/415
> 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.
> Deal with maxbuffer as it relates to proposals
> ----------------------------------------------
>
> Key: ZOOKEEPER-2939
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2939
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: jute, server
> Reporter: Andor Molnar
> Assignee: Andor Molnar
> Fix For: 3.5.4, 3.6.0
>
>
> Monitor real-time Jute buffer usage as it relates to proposals.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
