Dale Johnson commented on ZOOKEEPER-642:
It is a small instance.
When the machine becomes heavily loaded, the times go up quite a bit on
these messages, some into the thousands of milliseconds. But the
smaller values appear on a pretty regular basis.
Does the warning mean that it's not responded within a single tick?
The message as it is has a fairly low diagnostic value. I guess if they
happened with enough frequency and that was a signal to get more
zookeeper servers, or that the client hosts were too overloaded, it
could be more helpful.
> "exceeded deadline by N ms" floods logs
> Key: ZOOKEEPER-642
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-642
> Project: Zookeeper
> Issue Type: Bug
> Components: c client
> Affects Versions: 3.2.1
> Environment: virtualized linux - ec2 - ubuntu
> Reporter: Dale Johnson
> Fix For: 3.3.0
> More important zookeeper warnings are drown out by the following several
> times per minute:
> 2010-01-12 17:39:57,227:22317(0x4147eb90):zoo_w...@zookeeper_interest@1335:
> Exceeded deadline by 13ms
> Perhaps this is an issue with the way virtualized systems manage gettimeofday
> Maybe the current 10ms threshold could be pushed up a bit. I notice that 95%
> of the messages are below 50ms.
> Is there an obvious configuration change that I can make to fix this?
> config file below:
> # The number of milliseconds of each tick
> # The number of ticks that the initial
> # synchronization phase can take
> # The number of ticks that can pass between
> # sending a request and getting an acknowledgement
> # the directory where the snapshot is stored.
> # the port at which the clients will connect
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.