[
https://issues.apache.org/jira/browse/ZOOKEEPER-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16544766#comment-16544766
]
Michael Han commented on ZOOKEEPER-2184:
----------------------------------------
committed to master:
https://github.com/apache/zookeeper/commit/0a311873deb1847703c9b62716c626ce43d4ba48
branch-3.5:
https://github.com/apache/zookeeper/commit/1e65b9f4873fc995308972433ea8a664e98fe41f
> 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.4.7, 3.4.8, 3.4.9, 3.4.10, 3.5.0, 3.5.1, 3.5.2,
> 3.5.3, 3.4.11
> Environment: Ubuntu 14.04 host, Docker containers for Zookeeper &
> Kafka
> Reporter: Robert P. Thille
> Assignee: Andor Molnar
> Priority: Blocker
> Labels: easyfix, patch, pull-request-available
> Fix For: 3.6.0, 3.4.13, 3.5.5
>
> Attachments: ZOOKEEPER-2184.patch
>
> Time Spent: 10h
> Remaining Estimate: 0h
>
> 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
(v7.6.3#76005)
