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

["Hari Sekhon (JIRA)" <ji...@apache.org>]

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

Hari Sekhon commented on ZOOKEEPER-1922:
----------------------------------------

This has been reported for my check_zookeeper.pl Nagios plugin too:

https://github.com/harisekhon/nagios-plugins/issues/51

Apparently doing an 'srst' to reset the stats fixes it. I wouldn't be surprised if this was due to correcting a server's time in a sudden large step via ntpdate.

I've worked around this in my code by resetting the returned value to N/A and notifying the user to do 'srst'.

The more I think about this the more it seems like a minor ZooKeeper bug in not checking whether min latency < 0 for sanity.

I propose a simple fix that ZooKeeper check < 0 and if so do an internal 'srst' on it's stats.

> 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
(v6.3.4#6332)