[jira] Updated: (ZOOKEEPER-601) allow configuration of session timeout min/max bounds

["Patrick Hunt (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Hunt updated ZOOKEEPER-601:
-----------------------------------

    Attachment: ZOOKEEPER-601.patch

ZOOKEEPER-595 and ZOOKEEPER-617 are also addressed in this patch

1) the min/max session timeout can now be configured for a server (conf file/ jmx support enabled)
2) the "conf" 4letter word has been added (595)
3) cleanup some forrest doc (617)

During review please note:

1) new file added, be sure to svn add it
2) LeaderZKServer was missing a getServerID override, added it
3) test the "conf" 4 letter word
4) test jmx, verify you can see the params
5) tests added for everything
6) be sure to regenerate the forrest docs and commit


> 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
>
>
> 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.