[
https://issues.apache.org/jira/browse/ZOOKEEPER-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059402#comment-16059402
]
ASF GitHub Bot commented on ZOOKEEPER-2184:
-------------------------------------------
Github user rcillo commented on the issue:
https://github.com/apache/zookeeper/pull/150
This feature is highly valuable for the community. It could solve the
problem of every team deploying Kafka on the cloud. Kafka has a static
configuration with the IP addresses of Zookeeper nodes. If you need to replace
these nodes and consequently change their IP addresses, you need to change
Kafka configuratino file and then restart all Kafka nodes so that they will
reload the updated configuration.
If this feature is merged, everyone deploying Kafka on the cloud could
configure it using a load balancer address, that would be re-resolved from time
to time, so that new Zookeeper instances would be automatically reachable from
Kafka without the need of restarts. This would greatly improve the availability
of Kafka.
Looking forward to have this merged.
> 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.4, 3.6.0, 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.4.14#64029)
