You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Rajini Sivaram (JIRA)" <ji...@apache.org> on 2018/07/23 18:15:00 UTC

[jira] [Resolved] (KAFKA-7193) ZooKeeper client times out with localhost due to random choice of ipv4/ipv6

     [ https://issues.apache.org/jira/browse/KAFKA-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajini Sivaram resolved KAFKA-7193.
-----------------------------------
       Resolution: Fixed
         Reviewer: Ismael Juma
    Fix Version/s: 2.0.0

> ZooKeeper client times out with localhost due to random choice of ipv4/ipv6
> ---------------------------------------------------------------------------
>
>                 Key: KAFKA-7193
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7193
>             Project: Kafka
>          Issue Type: Bug
>          Components: zkclient
>    Affects Versions: 2.0.0
>            Reporter: Rajini Sivaram
>            Assignee: Rajini Sivaram
>            Priority: Major
>             Fix For: 2.0.0
>
>
> ZooKeeper client from version 3.4.13 doesn't handle connections to `localhost` very well. If ZooKeeper is started on 127.0.0.1 on a machine that has both ipv4 and ipv6 and a client is created using `localhost` rather than the IP address in the connection string, ZooKeeper client attempts to connect to ipv4 or ipv6 randomly with a fixed one second backoff if connection fails. With the default 6 second connection timeout in Kafka, this can result in client connection failures if ipv6 is chosen in consecutive address selections.
> Streams tests are failing intermittently as a result of this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)