ASF GitHub Bot commented on ZOOKEEPER-2184:

Github user anmolnar commented on the issue:

    > Should this PR be targeting branch-3.4 or target trunk and then backport 
to the 3.4 series?
    The original PR targets 3.4 which is explained in a comment from @fpj on 
the jira:
    > For the 3.5 branch, we will need a different patch because of the 
reconfiguration changes to StaticHostProvider. I'll work on it once the 3.4 
patch gets a +1.

> 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: Flavio Junqueira
>            Priority: Blocker
>              Labels: easyfix, patch
>             Fix For: 3.5.4, 3.4.12
>         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

Reply via email to