[
https://issues.apache.org/jira/browse/ZOOKEEPER-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822864#comment-15822864
]
ASF GitHub Bot commented on ZOOKEEPER-2184:
-------------------------------------------
GitHub user fpj opened a pull request:
https://github.com/apache/zookeeper/pull/150
ZOOKEEPER-2184: Zookeeper Client should re-resolve hosts when connection
attempts fail
This is a version of the patch for ZK-2184 for the 3.4 branch, compatible
with Java 6.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fpj/zookeeper ZK-2184
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/150.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #150
----
commit fbaa47e3a96f166cfae45070b0724780f13714e9
Author: fpj <[email protected]>
Date: 2017-01-14T16:58:15Z
ZOOKEEPER-2184: Zookeeper Client should re-resolve hosts when connection
attempts fail
----
> 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: Robert P. Thille
> Labels: easyfix, patch
> Fix For: 3.4.10, 3.5.3
>
> 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.4#6332)