[
https://issues.apache.org/jira/browse/ZOOKEEPER-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235401#comment-14235401
]
Brian Brazil commented on ZOOKEEPER-2093:
-----------------------------------------
The test failed in the QA is
org.apache.zookeeper.test.ReconfigTest.testPortChange
This worked on my machine and I note that another recent run also failed
(https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2447/testReport/org.apache.zookeeper.test/ReconfigTest/testPortChange/history/),
so I suspect this test is flaky.
> Expose cumulative latency and request count
> -------------------------------------------
>
> Key: ZOOKEEPER-2093
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2093
> Project: ZooKeeper
> Issue Type: Improvement
> Components: jmx, server
> Reporter: Brian Brazil
> Priority: Minor
> Labels: patch
> Attachments: export-cumulative-latency.patch
>
>
> Currently Zookeeper exposes min, max and average since server start request
> latency.
> It'd also be useful to be able to calculate latency over a given time period.
> This patch exposes the total latency, and count of number of request. By
> tracking how these values increase over time, your monitoring system can
> calculate the average latency over a given period of time.
> This only provides milliseconds, as that's what's currently there.
> I'm seeing a test failure on ClientPortBindTest.testBindByAddress, this
> appears to be due to my IPv6 setup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
