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 2014/02/26 15:11:19 UTC

[jira] [Commented] (CURATOR-83) LeaderLatch.close() doesn't fire LeaderLatchListener.notLeader()

    [ https://issues.apache.org/jira/browse/CURATOR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912945#comment-13912945 ] 

Jordan Zimmerman commented on CURATOR-83:
-----------------------------------------

Please provide a test that shows this problem.

> LeaderLatch.close() doesn't fire LeaderLatchListener.notLeader()
> ----------------------------------------------------------------
>
>                 Key: CURATOR-83
>                 URL: https://issues.apache.org/jira/browse/CURATOR-83
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.3.0
>            Reporter: Craig Muchinsky
>
> When closing a LeaderLatch, the order of cleanup is such that LeaderLatchListeners are not told they are no longer the leader. Within the finally block of the close() method the listener container is being cleared prior to the call to setLeadership(false). I believe simply reversing these calls will fix the problem.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)