Lei Zhang commented on ZOOKEEPER-642:
I have taken over Dale's responsibility of zookeeper. We have bumped up
tickTime to 20000 per Patrick's suggestion in another thread. Now we see these
"Exceeded deadline by 769ms" message every 10 seconds - I'm testing using
'cli_st localhost:<port>', on a VMware Linux machine that is mostly idle . I
echo Dale's comment:
The message as it is has a fairly low diagnostic value.
Since this message is at WARN level, I feel we need to do something. But what:
o bump up priority of zookeeper daemon
o check bug in client library
o check bug in zookeeper server
Somehow this doesn't smell like a real "Exceeded timeline" issue to me.
> "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.4.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.