curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cammckenzie <>
Subject [GitHub] curator pull request #157: Long session timeout issue
Date Tue, 14 Jun 2016 03:53:57 GMT
GitHub user cammckenzie opened a pull request:

    Long session timeout issue

    Fix for issue where LOST events were created at 4/3 of the session timeout rather than
at the end of session timeout.

You can merge this pull request into a Git repository by running:

    $ git pull long_session_timeout_issue

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #157
commit 8ec66e2ca4b9cbc546bef6e4eb44201042249b2f
Author: Cam McKenzie <>
Date:   2016-06-06T02:36:59Z

    Back to 3.2.0-SNAPSHOT

commit 93b140844f3fadae695fdf623f0e027ea5c4a1af
Author: Cam McKenzie <>
Date:   2016-06-06T02:37:52Z

    [maven-release-plugin] prepare release apache-curator-3.2.0

commit bc1960f13dc3cdc3ad2062385077637e139fc3e7
Author: Cam McKenzie <>
Date:   2016-06-06T02:38:02Z

    [maven-release-plugin] prepare for next development iteration

commit 1e07c779a682b15a1b2c604c55f80dcdaa21aef2
Author: Cam McKenzie <>
Date:   2016-06-07T00:40:16Z

     #noissue - Added unit test with long session timeout.

commit ef36275585fb883bb54db5a1396c58bb42b9b25b
Author: Cam McKenzie <>
Date:   2016-06-14T03:49:07Z

     #noissue - Modified connection state handling so that the poll period when in a SUSPENDED
state will match the remaining amount of time left until the session expires, rather than
2/3 of the session timeout. This will cause the LOST event to get triggered at the end of
the session timeout window. Updated a few unit tests that were failing intermitently due to
timing issues.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message