[
https://issues.apache.org/jira/browse/CURATOR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827058#comment-15827058
]
ASF GitHub Bot commented on CURATOR-171:
----------------------------------------
GitHub user oza reopened a pull request:
https://github.com/apache/curator/pull/195
[CURATOR-171] LeaderLatch isn't aware if it's own ephemeral node goes away
The root cause of the problem reported on CURATOR-171 is that LeaderLatch
is not aware of losing self znode after acquire lock. This PR fixes that
LeaderLatch is aware of my znode losing and marking itself "not leader".
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/oza/curator CURATOR-171
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/195.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #195
----
commit 3d9aed6a71a7bf59299a0b50f4469d200c29d01c
Author: Tsuyoshi Ozawa <[email protected]>
Date: 2017-01-12T09:24:19Z
CURATOR-171 - LeaderLatch isn't aware if it's own ephemeral node goes away
----
> LeaderLatch and LeaderSelector should support Revokable behavior
> ----------------------------------------------------------------
>
> Key: CURATOR-171
> URL: https://issues.apache.org/jira/browse/CURATOR-171
> Project: Apache Curator
> Issue Type: Improvement
> Components: Recipes
> Affects Versions: 3.2.1, 2.11.1
> Reporter: John Vines
> Priority: Minor
> Fix For: TBD
>
>
> Many Curator lock recipes support revoking. The Leader recipes should support
> this also as they use locking internally. See
> http://curator.apache.org/curator-recipes/shared-reentrant-lock.html -
> Revoking
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
