[
https://issues.apache.org/jira/browse/ZOOKEEPER-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845595#action_12845595
]
Hudson commented on ZOOKEEPER-601:
----------------------------------
Integrated in ZooKeeper-trunk #738 (See
[http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/738/])
> allow configuration of session timeout min/max bounds
> -----------------------------------------------------
>
> Key: ZOOKEEPER-601
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-601
> Project: Zookeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.2.1
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.3.0
>
> Attachments: ZOOKEEPER-601.patch, ZOOKEEPER-601.patch
>
>
> ZK servers currently enforce a min/max boundary on client session timeout
> relative to the ticktime setting, detailed here:
> http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#ch_zkSessions
> In general there are good reasons for this however in some cases, in
> particular with HBase region servers, we have seen a need to allow this bound
> to be set differently (higher). The Sun jvm can GC pause for very long times
> (in some cases we've seen 4 minutes even with the "realtime" gc.
> It would be good to allow this bound to be set via configuration parameters.
> Note: 4letterword and JMX integration would be needed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
