-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34394/
-----------------------------------------------------------
(Updated May 19, 2015, 5:20 a.m.)
Review request for kafka.
Bugs: KAFKA-1907
https://issues.apache.org/jira/browse/KAFKA-1907
Repository: kafka
Description
-------
KAFKA-1907 Set operation retry timeout on ZkClient. Also mark certain Kafka
threads as daemon to allow proper JVM shutdown
Diffs
-----
clients/src/main/java/org/apache/kafka/common/utils/Utils.java
f73eedb030987f018d8446bb1dcd98d19fa97331
core/src/main/scala/kafka/network/SocketServer.scala
edf6214278935c031cf493d72d266e715d43dd06
core/src/main/scala/kafka/server/DelayedOperation.scala
2ed9b467c2865e5717d7f6fd933cd09a5c5b22c0
core/src/main/scala/kafka/server/KafkaServer.scala
ea6d165d8e5c3146d2c65e8ad1a513308334bf6f
Diff: https://reviews.apache.org/r/34394/diff/
Testing (updated)
-------
ZkClient was recently upgraded to 0.5 version, as part of KAFKA-2169. The 0.5
version of ZkClient contains an enhancement which allows passing of operation
retry timeout https://github.com/sgroschupf/zkclient/pull/29. This now allows
us to fix the issue reported in
https://issues.apache.org/jira/browse/KAFKA-1907.
The commit here passes the operation retry timeout while creating the ZkClient
instances. The commit was contains a change to mark certain threads as daemon
to allow a clean shutdown of the Kafka server when the zookeeper instance has
gone done first.
I've locally tested that shutting down Kafka, after zookeeper has already
shutdown, works fine now (it tries to reconnect to zoookeeper for a maximum of
5 seconds before cleanly shutting down). I've also checked that shutting down
Kafka first, when zookeeper is still up, works fine too.
Thanks,
Jaikiran Pai
