We have three brokers on our production cluster. I noticed two of them somehow got offline and then re-registered with zookeeper and got back online. It seems the issue was caused by some zookeeper issue. So I want to know what may be the possible cases of the issue. If I want to reproduce the issue, is there any way to do it? Thanks.
When ZK resumes from a soft failure, like a GC, it will mark the ephemeral nodes as session timed out, and the brokers will try to re-register upon receiving the session timeout. You can re-produce this issue by signal pause the ZK process.
Guozhang On Fri, Feb 14, 2014 at 12:15 PM, Yu, Libo <[EMAIL PROTECTED]> wrote:
In our case, two brokers were offline. When the first broker was offline, that would trigger a rebalance. When the second broker was offline, if the consumers were in the process of rebalance, what do we expect? Is the second rebalance request queued?
Yes, it will be queued, and the second rebalance will start right after the first one. On Fri, Feb 21, 2014 at 8:50 AM, Yu, Libo <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext