[
https://issues.apache.org/jira/browse/KAFKA-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536281#comment-14536281
]
Igor Maravić commented on KAFKA-2169:
-------------------------------------
[~parth.brahmbhatt] If you look at the stack trace more closely, you can see
that you're swallowing that exact exception.
As far as I can see, all the exceptions, that are thrown while handling
watchers are happily swallowed by ClientCnx in zookeeper and hence ignored by
Kafka. In this particular case Kafka is just ignoring fatal exception, and it
happily allows zkClient to shutdown.
Since the reconnect event is run as a Zookeeper watcher, on the Zookeeper's
ClientCnxn Event Thread, all the exception thrown from there are just swallowed
here:
https://github.com/apache/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/ClientCnxn.java#L543
I'll open up a new JIRA ticket for this.
> Upgrade to zkclient-0.5
> -----------------------
>
> Key: KAFKA-2169
> URL: https://issues.apache.org/jira/browse/KAFKA-2169
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.0
> Reporter: Neha Narkhede
> Assignee: Parth Brahmbhatt
> Priority: Critical
>
> zkclient-0.5 is released
> http://mvnrepository.com/artifact/com.101tec/zkclient/0.5 and has the fix for
> KAFKA-824
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
