curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-518) Curator. LeaderSelector. Two successive calls to interruptLeadership() will break autoRequeue.
Date Mon, 15 Apr 2019 15:03:00 GMT

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

Jordan Zimmerman commented on CURATOR-518:
------------------------------------------

Thank you. A PR with a fix would be appreciated.

> Curator. LeaderSelector. Two successive calls to interruptLeadership() will break autoRequeue.
> ----------------------------------------------------------------------------------------------
>
>                 Key: CURATOR-518
>                 URL: https://issues.apache.org/jira/browse/CURATOR-518
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>    Affects Versions: 4.0.1, 4.2.0
>         Environment: Windows 8, JRE 1.8.0_181
>            Reporter: Bulatov Oleg
>            Priority: Major
>              Labels: newbie
>
> h1. Curator. LeaderSelector. Two successive calls to interruptLeadership() will break
autoRequeue
> If we set autoRequeue to TRUE. But during execution interruptLeadership() will be called
from another thread before internalRequeue() completed its work. Then it will break recursive
call to internalRequeue(), so that client will not ask for leadership and get stuck.
> We can solve this problem if we check hasLeadership() before calling interruptLeadership().
But it is strange that such check curator library does not do internally.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message