curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Hjalmar Herje (JIRA)" <>
Subject [jira] [Commented] (CURATOR-264) Leader election: Duplicate ephemeral nodes with same owner id
Date Wed, 23 Sep 2015 08:59:04 GMT


Ole Hjalmar Herje commented on CURATOR-264:

I have tested with the new version and I can confirm that it was a issue with the namespace.
Curator 2.8.0 tries to get children for path:
and this results in NoNode:
Branch CURATOR-264:

and everything seems to be OK. 

> Leader election: Duplicate ephemeral nodes with same owner id
> -------------------------------------------------------------
>                 Key: CURATOR-264
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework, Recipes
>    Affects Versions: 2.8.0
>            Reporter: Ole Hjalmar Herje
>            Assignee: Jordan Zimmerman
>            Priority: Blocker
>             Fix For: 2.9.1
>         Attachments: testLog.txt, zkNodes.txt, zkTransactionLog.txt
> We sometimes experience failure in our leader-election functionality when we have network
issues. When this situation occurs we see that there are two ephemeral nodes in the zookeeper
cluster for the same session but there is no active leader. 
> I have managed to recreate the same scenario by running a test locally and use iptables
to simulate network issues. The debug log (see attachment) shows that findAndDeleteProtectedNodeInBackground
does not delete the node because processResult in FindProtectedNodeCB receives a -101 (NoNode)
resultcode. I suspect this can happen if the read is not synched? (
> This also seems to be related to: 
> and

This message was sent by Atlassian JIRA

View raw message