[ZOOKEEPER-642] "exceeded deadline by N ms" floods logs

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.1
• Fix Version/s: 3.5.0
• Component/s: c client
• Labels: patch

Environment

virtualized linux - ec2 - ubuntu

• Assignee: Marc Celani
• Reporter: Dale Johnson
• Created: 13/Jan/10 01:52
• Updated: 11/May/12 11:00
• Resolved: 11/May/12 05:55

Description

More important zookeeper warnings are drown out by the following several times per minute:

2010-01-12 17:39:57,227:22317(0x4147eb90):ZOO_WARN@zookeeper_interest@1335: Exceeded deadline by 13ms

Perhaps this is an issue with the way virtualized systems manage gettimeofday results?

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:

1. The number of milliseconds of each tick
   tickTime=2000
2. The number of ticks that the initial
3. synchronization phase can take
   initLimit=10
4. The number of ticks that can pass between
5. sending a request and getting an acknowledgement
   syncLimit=5
6. the directory where the snapshot is stored.
   dataDir=/mnt/zookeeper
7. the port at which the clients will connect
   clientPort=2181

server.1=hbase.1:2888:3888
server.2=hbase.2:2888:3888
server.3=hbase.3:2888:3888
server.4=hbase.4:2888:3888
server.5=hbase.5:2888:3888