[ https://issues.apache.org/jira/browse/ZOOKEEPER-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663310#action_12663310 ]
Hudson commented on ZOOKEEPER-258: ---------------------------------- Integrated in ZooKeeper-trunk #194 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/194/]) . docs incorrectly state max client timeout as 60 seconds (it's based on server ticktime). (phunt via mahadev) > docs incorrectly state max client timeout as 60 seconds (it's based on server > ticktime) > --------------------------------------------------------------------------------------- > > Key: ZOOKEEPER-258 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-258 > Project: Zookeeper > Issue Type: Bug > Components: documentation > Affects Versions: 3.0.0, 3.0.1 > Reporter: Patrick Hunt > Assignee: Patrick Hunt > Priority: Minor > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-258.patch > > > The docs incorrectly state the max client timeout as 60 seconds. > http://hadoop.apache.org/zookeeper/docs/r3.0.1/zookeeperProgrammers.html#ch_zkSessions > the current server code has the following logic: > if (sessionTimeout < zk.tickTime * 2) { > sessionTimeout = zk.tickTime * 2; > } > if (sessionTimeout > zk.tickTime * 20) { > sessionTimeout = zk.tickTime * 20; > } > So really the docs should say max is 20*tickTime -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.