You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "maoling (JIRA)" <ji...@apache.org> on 2018/07/02 12:35:00 UTC

[jira] [Commented] (ZOOKEEPER-1922) Negative min latency value

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529815#comment-16529815 ] 

maoling commented on ZOOKEEPER-1922:
------------------------------------

[~harisekhon][~tonyseek][~jpotter]
since [ZOOKEEPER-1366 |https://issues.apache.org/jira/browse/ZOOKEEPER-1366] has replaced *System.currentTimeMillis* to *System.nanoTime*,this issue can not be reproduced. Am I right?


> Negative min latency value
> --------------------------
>
>                 Key: ZOOKEEPER-1922
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1922
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.4.6
>            Reporter: J Potter
>            Priority: Minor
>
> We're seeing the output of stat on one node return a negative value for min latency time:
> stat 
> Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT
> Clients:
> ...
> Latency min/avg/max: -477/149/261002
> (The max value seems suspicious, too.)
> Figured I'd report this, as I don't see any mention of it online or in other bug reports. Maybe negative values shouldn't be recorded?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)