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 B820A17D21 for ; Mon, 12 Jan 2015 20:32:33 +0000 (UTC) Received: (qmail 50786 invoked by uid 500); 12 Jan 2015 20:32:35 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 50740 invoked by uid 500); 12 Jan 2015 20:32:35 -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 50728 invoked by uid 99); 12 Jan 2015 20:32:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jan 2015 20:32:35 +0000 Date: Mon, 12 Jan 2015 20:32:34 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CURATOR-175) If zookeeper is down when discovery is started, it fails to register when the zookeeper comes up for the first time. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CURATOR-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274122#comment-14274122 ] ASF GitHub Bot commented on CURATOR-175: ---------------------------------------- Github user asfgit closed the pull request at: https://github.com/apache/curator/pull/58 > If zookeeper is down when discovery is started, it fails to register when the zookeeper comes up for the first time. > -------------------------------------------------------------------------------------------------------------------- > > Key: CURATOR-175 > URL: https://issues.apache.org/jira/browse/CURATOR-175 > Project: Apache Curator > Issue Type: Bug > Components: Framework > Affects Versions: 2.7.0 > Reporter: Gopi Kori > Priority: Minor > Labels: curator-x-discovery > > If zookeeper is down when discovery is started, it fails to register when the zookeeper comes up for the first time. > However, if the zookeeper is restarted again, discovery will connect and register the service instance correctly. > This happens because org.apache.curator.x.discovery.details.ServiceDiscoveryImpl.stateChanged() considers only ConnectionState.RECONNECTED state and not ConnectionState.CONNECTED. This causes the first connection to be ignored, while subsequent connection recoveries work fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)