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-202) LeaderSelector node is not removed on connection loss if reconnected to the same session
Date Thu, 02 Apr 2015 20:44:53 GMT

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

Jordan Zimmerman commented on CURATOR-202:
------------------------------------------

Are you using LeaderSelectorListenerAdapter? This is the recommended approach. Otherwise,
you must throw CancelLeadershipException() or release leadership when there is a connection
problem. If neither of these solves your problem please provide a test that exhibits the issue.

> LeaderSelector node is not removed on connection loss if reconnected to the same session
> ----------------------------------------------------------------------------------------
>
>                 Key: CURATOR-202
>                 URL: https://issues.apache.org/jira/browse/CURATOR-202
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.7.1
>            Reporter: Sergey Serebryanik
>            Priority: Minor
>
> Leader selection fails when connection is lost but restored before session timed out.
> TC:
> * the client looses connection to the zookeeper server
> * the client looses leadership
> * the client reconnects to the zookeeper server using the same session
> * the leader node wasn't deleted because the connection was not available on deleteOurPath()
call, and because the client had reconnected to the same session, so the ephemeral node wasn't
deleted by zookeeper
> * the client creates the new node
> * no one is the leader because the old leader node stays forever.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message