Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Zookeeper >> mail # dev >> negotiated timeout


Copy link to this message
-
negotiated timeout
Hi,
hbase 0.90.1 uses zookeeper 3.3.2
I specified:
<property>
<name>zookeeper.session.timeout</name>
<value>490000</value>
</property>

In zookeeper log I see:
2011-03-24 19:58:09,499 INFO org.apache.zookeeper.server.NIOServerCnxn:
Client attempting to establish new session at /10.202.50.111:50325
2011-03-24 19:58:09,499 INFO org.apache.zookeeper.server.NIOServerCnxn:
Established session 0x12ebb99d686a012 with negotiated timeout 60000 for
client /10.202.50.112:62386
2011-03-24 19:58:09,499 INFO org.apache.zookeeper.server.NIOServerCnxn:
Client attempting to establish new session at /10.202.50.112:62387
2011-03-24 19:58:09,499 INFO
org.apache.zookeeper.server.PrepRequestProcessor: Got user-level
KeeperException when processing sessionid:0x12ebb99d686a012 type:create
cxid:0x1 zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a Error
Path:/hbase Error:KeeperErrorCode = NodeExists for /hbase
2011-03-24 19:58:09,499 INFO org.apache.zookeeper.server.NIOServerCnxn:
Established session 0x12ebb99d686a013 with negotiated timeout 60000 for
client /10.202.50.111:50324

Can someone tell me how the negotiated timeout of 60000 was computed ?

Thanks
+
Mahadev Konar 2011-03-24, 22:43
+
Ted Yu 2011-03-24, 22:49
+
Patrick Hunt 2011-03-24, 22:50
+
Ted Yu 2011-03-24, 23:00
+
Patrick Hunt 2011-03-24, 23:15
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB