I think you may be asking a slightly different question. If a broker falls out of ISR and does not rejoin the ISR, it may point to some bottleneck (e.g. local IO), fewer partitions for large topics or some fatal error causing the ReplicaFetcherThread to die. Just restarting the broker without knowing the root cause might not always make the broker rejoin ISR.
Thanks all. In this case, restarting the broker fixed it. It was due to an usual high volume of messages in one topic. On Sep 27, 2013, at 12:16 AM, Neha Narkhede <[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