curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julio Lopez (JIRA)" <>
Subject [jira] [Updated] (CURATOR-16) LeaderSelector does not (auto)requeue on session expired
Date Mon, 20 May 2013 16:29:16 GMT


Julio Lopez updated CURATOR-16:

    Attachment: CURATOR-16-test.patch

Test for CURATOR-16.

This demonstrates the issue.  It required forcing the ZK client to fail deterministically,
otherwise the probability of the appropriate exception being propagated up is very low (but

Also, the test passes with the previously sent patch.

> LeaderSelector does not (auto)requeue on session expired
> --------------------------------------------------------
>                 Key: CURATOR-16
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.0.0-incubating
>            Reporter: Julio Lopez
>            Assignee: Jordan Zimmerman
>             Fix For: 2.0.2-incubating
>         Attachments: CURATOR-16.patch, CURATOR-16-test.patch
> If mutex. acquire() throws a KeeperException.SessionExpiredException in LeaderSelector.doWork(),
the exception is not handled in LeaderSelector.doWorkLoop(), causing the loop to terminate
even when autoRequeue is true.

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:

View raw message