You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ryan P (JIRA)" <ji...@apache.org> on 2017/01/18 17:16:26 UTC
[jira] [Commented] (KAFKA-4041) kafka unable to reconnect to
zookeeper behind an ELB
[ https://issues.apache.org/jira/browse/KAFKA-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828420#comment-15828420 ]
Ryan P commented on KAFKA-4041:
-------------------------------
This is actually the result of a ZK bug which is being actively worked on here:
https://issues.apache.org/jira/browse/ZOOKEEPER-2184
> kafka unable to reconnect to zookeeper behind an ELB
> ----------------------------------------------------
>
> Key: KAFKA-4041
> URL: https://issues.apache.org/jira/browse/KAFKA-4041
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.9.0.1, 0.10.0.1
> Environment: RHEL EC2 instances
> Reporter: prabhakar
> Priority: Blocker
>
> Kafka brokers are unable to connect to zookeeper which is behind an ELB.
> Kafka is using zkClient which is caching the IP address of zookeeper and even when there is a change in the IP for zookeeper it is using the Old zookeeper IP.
> The server.properties has a DNS name. Ideally kafka should resolve the IP using the DNS in case of any failures connecting to the broker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)