Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 56F44200B3C for ; Wed, 13 Jul 2016 20:41:48 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5573B160A6A; Wed, 13 Jul 2016 18:41:48 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 74EBB160A62 for ; Wed, 13 Jul 2016 20:41:47 +0200 (CEST) Received: (qmail 59519 invoked by uid 500); 13 Jul 2016 18:41:46 -0000 Mailing-List: contact user-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@curator.apache.org Delivered-To: mailing list user@curator.apache.org Received: (qmail 59509 invoked by uid 99); 13 Jul 2016 18:41:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jul 2016 18:41:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 383431A5DE3 for ; Wed, 13 Jul 2016 18:41:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.999 X-Spam-Level: * X-Spam-Status: No, score=1.999 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, SPF_PASS=-0.001] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id qLQd2gTIDW80 for ; Wed, 13 Jul 2016 18:41:44 +0000 (UTC) Received: from mo01c.lpsvcs.com (mo01c.lpsvcs.com [206.201.66.78]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id D345C5FE21 for ; Wed, 13 Jul 2016 18:41:43 +0000 (UTC) X-Disclaimer: Default Received: from unknown (HELO JTCLPSWEXCAH03.lpsvcs.com) ([10.48.139.22]) by jtc-smtp01.lpsvcs.com with ESMTP/TLS/AES256-SHA; 13 Jul 2016 14:41:33 -0400 Received: from JTCLPSWEXMBH04.lpsvcs.com ([fe80::7588:4c36:d3fe:edd6]) by jtclpswexcah03 ([10.48.139.22]) with mapi id 14.03.0266.001; Wed, 13 Jul 2016 14:41:33 -0400 From: "Cantrell, Curtis" To: "user@curator.apache.org" Subject: RE: Problem with LeaderSelector 2.7.1 Thread-Topic: Problem with LeaderSelector 2.7.1 Thread-Index: AdHdBXqkLOaN6nsFRK+IbkcQwc7efQAMD3Zg Date: Wed, 13 Jul 2016 18:41:33 +0000 Message-ID: <58541717BBD8834B8AA650F2108759222F007ACF@JTCLPSWEXMBH04.lpsvcs.com> References: <58541717BBD8834B8AA650F2108759222F0079D9@JTCLPSWEXMBH04.lpsvcs.com> In-Reply-To: <58541717BBD8834B8AA650F2108759222F0079D9@JTCLPSWEXMBH04.lpsvcs.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.48.162.222] Content-Type: multipart/alternative; boundary="_000_58541717BBD8834B8AA650F2108759222F007ACFJTCLPSWEXMBH04l_" MIME-Version: 1.0 archived-at: Wed, 13 Jul 2016 18:41:48 -0000 --_000_58541717BBD8834B8AA650F2108759222F007ACFJTCLPSWEXMBH04l_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable It looks like maybe there are two Fixes that affect my problem. CURATOR-26= 4 and CURATOR-247. Has CURATOR-247 been merge to the 2.X branch or do = I need to update my zookeeper to 3.5 in order to get the fix? Leader election: Duplicate ephemeral nodes with same owner id https://issues.apache.org/jira/browse/CURATOR-264 We sometimes experience failure in our leader-election functionality when w= e 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. Extend Curator's connection state to support SESSION_LOST https://issues.apache.org/jira/browse/CURATOR-247 Curator has a connection state for LOST that confuses users. It does not me= an that the session is lost. Instead it means that the retry policy has giv= en up retrying The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. --_000_58541717BBD8834B8AA650F2108759222F007ACFJTCLPSWEXMBH04l_ Content-Type: text/html; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable

It looks like maybe there are two Fixes that af= fect my problem.  CURATOR-264 and CURATOR-247.    =   Has CURATOR-247 been merge to the 2.X branch or do I need to update my zookeeper to 3.5 in order to get the fix?

Leader election: Duplicate ephemeral nodes with same= owner id

https://issues.apache.org/jira/browse/CURATOR-264<= /p>

 

We sometimes experience fai= lure 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.

Extend Curator's connection state to support = SESSION_LOST

https://issues.apache.org/jira/browse/CURATOR-247<= /p>

 

Curator has a connection st= ate for LOST that confuses users. It does not mean that th= e session is lost. Instead it means that the retry policy has given up retrying

 

 

The information contained in this message is proprietary and/or confid= ential. If you are not the intended recipient, please: (i) delete the messa= ge and all copies; (ii) do not disclose, distribute or use the message in a= ny manner; and (iii) notify the sender immediately. In addition, please be = aware that any message addressed to our domain is subject to archiving and = review by persons other than the intended recipient. Thank you. --_000_58541717BBD8834B8AA650F2108759222F007ACFJTCLPSWEXMBH04l_--