Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Sun, 19 Feb 2017 16:38:44 +0000 (UTC)
From: "Benjamin Reed (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.12828194.1431042372000.6616.1487522324981@Atlassian.JIRA>
In-Reply-To: <JIRA.12828194.1431042372000@Atlassian.JIRA>
References: <JIRA.12828194.1431042372000@Atlassian.JIRA> <JIRA.12828194.1431042372019@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ZOOKEEPER-2184) Zookeeper Client should
 re-resolve hosts when connection attempts fail
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 19 Feb 2017 16:38:52 -0000


    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873747#comment-15873747 ] 

Benjamin Reed commented on ZOOKEEPER-2184:
------------------------------------------

another option would be to have a  background worker that periodically wakes up and re-resolves hosts every few minutes. if we ever get a connection failure we could use that to kick the background worker to run right away.

> Zookeeper Client should re-resolve hosts when connection attempts fail
> ----------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2184
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2184
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.4.6, 3.5.0
>         Environment: Ubuntu 14.04 host, Docker containers for Zookeeper & Kafka
>            Reporter: Robert P. Thille
>            Assignee: Flavio Junqueira
>              Labels: easyfix, patch
>             Fix For: 3.5.3, 3.4.11
>
>         Attachments: ZOOKEEPER-2184.patch
>
>
> Testing in a Docker environment with a single Kafka instance using a single Zookeeper instance. Restarting the Zookeeper container will cause it to receive a new IP address. Kafka will never be able to reconnect to Zookeeper and will hang indefinitely. Updating DNS or /etc/hosts with the new IP address will not help the client to reconnect as the zookeeper/client/StaticHostProvider resolves the connection string hosts at creation time and never re-resolves.
> A solution would be for the client to notice that connection attempts fail and attempt to re-resolve the hostnames in the connectString.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)