[
https://issues.apache.org/jira/browse/KAFKA-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15616914#comment-15616914
]
Rekha Joshi edited comment on KAFKA-3893 at 11/30/16 2:58 AM:
--------------------------------------------------------------
We saw it too in Kafka 0.8.x and upgraded to Kafka 0.9.x and continued seeing
this issue, especially in AWS.This was seen in AWS especially if you configure
zookeeper connect property with zookeeper ELB instead of individual IP:port
set. When we reversed zookeeper connect with zookeeper IP:port instead of
zookeeper ELB, it worked great.
It would be great(can help) if Apache Kafka/Confluent FAQ can be updated to
note this.
Thanks
Rekha
was (Author: rekhajoshm):
We saw it too in Kafka 0.8.x and upgraded to Kafka 0.9.x and continued seeing
this issue.Going with workarounds.But it would be great(can help) if this is
documented clearly on Apache Kafka/Confluent FAQ.
Thanks
Rekha
> Kafka Borker ID disappears from /borkers/ids
> --------------------------------------------
>
> Key: KAFKA-3893
> URL: https://issues.apache.org/jira/browse/KAFKA-3893
> Project: Kafka
> Issue Type: Bug
> Reporter: chaitra
> Priority: Critical
>
> Kafka version used : 0.8.2.1
> Zookeeper version: 3.4.6
> We have scenario where kafka 's broker in zookeeper path /brokers/ids just
> disappears.
> We see the zookeeper connection active and no network issue.
> The zookeeper conection timeout is set to 6000ms in server.properties
> Hence Kafka not participating in cluster
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
