Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3012917D07 for ; Thu, 12 Feb 2015 16:02:34 +0000 (UTC) Received: (qmail 94562 invoked by uid 500); 12 Feb 2015 16:02:12 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 94515 invoked by uid 500); 12 Feb 2015 16:02:12 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 94502 invoked by uid 99); 12 Feb 2015 16:02:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2015 16:02:12 +0000 Date: Thu, 12 Feb 2015 16:02:11 +0000 (UTC) From: "Rodrigo Nogueira (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CURATOR-188) Cannot determine the leader if zookeeper leader fails MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Rodrigo Nogueira created CURATOR-188: ---------------------------------------- Summary: Cannot determine the leader if zookeeper leader fails Key: CURATOR-188 URL: https://issues.apache.org/jira/browse/CURATOR-188 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 problems. 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 inconsistent. 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, _c_54a126d3-31e8-464f-9216-5e0ad23fad1b-lock-0000000004] 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 (v6.3.4#6332)