ZooKeeper is only a canary, telling the region server that it was partionned from the cluster for longer than the default timeout somehow, usually because of GC pauses. You should see lines like "slept for x, long than y" messages before what you pasted.
J-D On Wed, Jul 21, 2010 at 2:49 PM, Steve Kuo <kuosen...@gmail.com> wrote: > It's shaping up to be zookeeper problem. The UI showed only 4 RS's running > but when I went on one of the nodes, I saw one of the missing RS was still > running. This RS eventually got terminated due to the following exception > and proceeded to shut down. > > I will search on all zookeeper related threads. Any quick help will be most > appreciated. > > 2010-07-21 14:42:22,074 WARN org.apache.zookeeper.ClientCnxn: Exception > closing session 0x129f24e134a002b to sun.nio.ch.selectionkeyi...@15e232b5 > java.io.IOException: TIMED OUT > at > org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:906) > 2010-07-21 14:42:22,075 WARN org.apache.zookeeper.ClientCnxn: Exception > closing session 0x129f24e134a002d to sun.nio.ch.selectionkeyi...@d2f0e06 > java.io.IOException: TIMED OUT > at > org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:906) >
