kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Omid Aladini <omidalad...@gmail.com>
Subject When ZooKeeper quorum is down
Date Tue, 03 Feb 2015 12:23:44 GMT

Reading the official FAQ, I bumped into this paragraph:

Once the Zookeeper quorum is down, brokers could result in a bad state and
> could not normally serve client requests, etc. Although when Zookeeper
> quorum recovers, the Kafka brokers should be able to resume to normal state
> automatically, there are still a few corner cases the they cannot and a
> hard kill-and-recovery is required to bring it back to normal. Hence it is
> recommended to closely monitor your zookeeper cluster and provision it so
> that it is performant.

What are the corner cases exactly? Any JIRA tickets to explore? How do the
corner cases relate to the ZooKeeper cluster being "performant" and
"closely monitored"? I'm specifically interested in the inevitable scenario
that the ZK leader exits / dies and the quorum goes down momentarily (due
to hardware failure, rolling restart, etc).


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message