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

Posted to dev@curator.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/22 18:26:00 UTC

[jira] [Commented] (CURATOR-171) LeaderLatch and LeaderSelector should support Revokable behavior

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

ASF GitHub Bot commented on CURATOR-171:
----------------------------------------

Github user jacky1193610322 commented on the issue:

    https://github.com/apache/curator/pull/195
  
    when I want to change leader manually, I can delete the leader node manually, let the others become the leader.


> 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
(v7.6.3#76005)