[ https://issues.apache.org/jira/browse/HBASE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692165#comment-13692165 ]
Sergey Shelukhin commented on HBASE-8785: ----------------------------------------- That is if maxSessionTimeout defined on ZK, not in our config. I was running integration tests and saw that negotiated timeout is 40s., coming from ZK (tick * 20?) So at least the comment needs to be changed imo. > revise zookeeper session timeout setting > ---------------------------------------- > > Key: HBASE-8785 > URL: https://issues.apache.org/jira/browse/HBASE-8785 > Project: HBase > Issue Type: Improvement > Affects Versions: 0.95.1 > Reporter: Sergey Shelukhin > Fix For: 0.95.2 > > > Current ZK session timeout is set to 90sec., and the comment in the doc says: > "This setting becomes zookeeper's 'maxSessionTimeout'". However, this comment > is misleading - it doesn't always become maxSessionTimeout, min(our timeout, > maxSessionTimeout) is chosen. Moreover, the default maxSessionTimeout in ZK > that I'm looking at is 40s, so this setting doesn't do anything. > Additionally, 40s. seems like a lot of time. > 1) Should the comment be changed to tell the user to change ZK config if they > want higher timeout? > 2) Should the setting be revised down? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira