curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Trott (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-83) LeaderLatch.close() doesn't fire LeaderLatchListener.notLeader()
Date Thu, 06 Mar 2014 02:44:46 GMT

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

David Trott commented on CURATOR-83:
------------------------------------

Sorry looks like I duplicated this issue (issue #92) but I have attached a pull request to
resolve.

> 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.2#6252)

Mime
View raw message