curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Scott Carr (JIRA)" <>
Subject [jira] [Commented] (CURATOR-188) Cannot determine the leader if zookeeper leader fails
Date Wed, 26 Oct 2016 17:55:58 GMT


Kevin Scott Carr commented on CURATOR-188:


Seeing this similar behavior.  If we stop the LeaderSelector on all 3 systems, the path still
exists.  When we start one instance, it gets the Lock exception You do not own the lock, and
there is not a Leader.

I did a rmr on the parent path, and started the instance, and then we were elected leader,
and things progressed.

Still researching how it got into this state.

> Cannot determine the leader if zookeeper leader fails
> -----------------------------------------------------
>                 Key: CURATOR-188
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.7.1
>            Reporter: Rodrigo Nogueira
> Hi,
> I'm trying to upgrade the curator framework from 2.6.0 to 2.7.1, but I'm having some
> In the 2.6.0 version almost everything works fine, but the ServiceDiscovery.updateService()
that is already fixed in the 2.7.1.
> In the 2.7.1 version, when I kill the zookeeper leader, my path for leader election becomes
> For instance, I have three apps registered in the leader path (/com/myapp/leader/):
> [_c_85089ba7-0819-40a2-90b5-640bcb5e9e68-lock-0000000003, _c_070619f6-539e-4784-8068-bdc66d2a25bc-lock-0000000005,
> After killing the zookeeper leader, what I got in the /com/myapp/leader/ is:
> [_c_648d5311-a59c-4bc4-bf32-c0605dea9b6a-lock-0000000007, _c_85089ba7-0819-40a2-90b5-640bcb5e9e68-lock-0000000003,
_c_f51f9660-3cbf-4ba8-8dba-c1e04ca14a93-lock-0000000008, _c_49696b77-e45a-40b6-8feb-96623c67fd85-lock-0000000006]
> Sometimes I got more nodes (five or six).
> I'm aware that Curator removes and adds all nodes when a zookeeper node fails. But it
seems that the previous nodes are not being removed correctly.
> Is that the expected behavior ? 

This message was sent by Atlassian JIRA

View raw message