Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # dev >> [jira] [Commented] (KAFKA-1082) zkclient dies after UnknownHostException in zk reconnect


Copy link to this message
-
[jira] [Commented] (KAFKA-1082) zkclient dies after UnknownHostException in zk reconnect

    [ https://issues.apache.org/jira/browse/KAFKA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793853#comment-13793853 ]

Jun Rao commented on KAFKA-1082:
--------------------------------

Thanks for the patch. Commented on the RB. Also, we need to make sure the new zkclient 0.4 jar is backward compatible, i.e., it can be a drop-in replacement of the 0.3 and 0.1 jar without causing any runtime issues. I did some verification on the broker and the consumer side. It does seem to be binary backward compatible, even tough there is a new method in the state change listener interface. It would be good if you can confirm this.

> zkclient dies after UnknownHostException in zk reconnect
> --------------------------------------------------------
>
>                 Key: KAFKA-1082
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1082
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8, 0.7.2
>            Reporter: Anatoly Fayngelerin
>         Attachments: KAFKA-1082.patch
>
>
> Moving this here from the dev list:
> I've run into the following issue with the Kafka server. The zkclient lib seems to die silently if there is an UnknownHostException(or any IOException) while reconnecting the ZK session. I've filed a bug about this with the zkclient lib(https://github.com/sgroschupf/zkclient/issues/23). The ramifications for Kafka were the silent loss of all ephemeral nodes associated with the affected process.
> It is fairly easy to reproduce this locally using the following steps:
> -- Configure a local kafka broker to connect to a local ZK instance using a DNS alias(e.g.  add "127.0.0.1 kafka-test-dns" to your /etc/hosts)
> -- Start the broker, observe that ephemeral nodes have been added to ZK
> -- Suspend the broker process, preventing it from sending heartbeats to the ZK instance. Observe the loss of ephemeral nodes in ZK.
> -- Remove the DNS alias(e.g. comment out the /etc/hosts line).
> -- Upon resuming the broker, the UknownHostException is logged. After this point, the server cannot re-establish its ZK connection. Re-enabling the alias, for example, does not resume normal operation. The broker continues accepting requests, without participating in the ZK protocols.

--
This message was sent by Atlassian JIRA
(v6.1#6144)

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB