[
https://issues.apache.org/jira/browse/ZOOKEEPER-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254483#comment-16254483
]
ASF GitHub Bot commented on ZOOKEEPER-2939:
-------------------------------------------
Github user phunt commented on the issue:
https://github.com/apache/zookeeper/pull/415
I didn't look at this in much depth yet but one obvious things struck me -
you are missing the reset capability. See how we handle latency tracking in the
beans.
We try to keep jmx, 4lw and jetty interfaces (new in 3.5) in lock step wrt
the metrics they provide. What do you think, do you want to try to include that
in this patch or create separate JIRA(s) to track/address?
> 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
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
