[
https://issues.apache.org/jira/browse/HBASE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691026#comment-13691026
]
stack commented on HBASE-8785:
------------------------------
Looking in zk src, I see this in 3.4.5:
{code}
src//java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java:
return maxSessionTimeout == -1 ? tickTime * 20 : maxSessionTimeout;
{code}
If maxSessionTimeout is defined, it is what is used (Some context:
http://mail-archives.apache.org/mod_mbox/zookeeper-dev/201109.mbox/%[email protected]%3E)
Regards 40s, yeah, it is a long time but what JD says. It used to be 180s in
0.94 and was made 90s in trunk.
> 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
