You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2013/06/10 17:00:26 UTC

[jira] [Resolved] (CURATOR-16) LeaderSelector does not (auto)requeue on session expired

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

Jordan Zimmerman resolved CURATOR-16.
-------------------------------------

    Resolution: Fixed
    
> LeaderSelector does not (auto)requeue on session expired
> --------------------------------------------------------
>
>                 Key: CURATOR-16
>                 URL: https://issues.apache.org/jira/browse/CURATOR-16
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.0.0-incubating
>            Reporter: Julio Lopez
>             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: http://www.atlassian.com/software/jira