You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/11/21 15:01:00 UTC
[jira] [Resolved] (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:all-tabpanel ]
Ismael Juma resolved KAFKA-4041.
--------------------------------
Resolution: Fixed
Marking as a duplicate of KAFKA-5473. In that JIRA, we will recreate the `ZooKeeper` instance if there's an issue connecting and should hopefully fix this issue too.
> 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.4.14#64029)