Sorry if this had been answered before. Although, I couldn't find any information besides "controlled shutdown of broker", which, I believe not fully applies here.
Could anyone suggest what would be the safest strategy to shut down kafka cluster? Should brokers be brought down one-by-one or simultaneously? Does this strategy change depend on whether "controlled shutdown" is on?
According to my brief observation, ad-hoc broker shutdown (mix and match INT, TERM and KILL signals to the most resilient brokers) results in prolonged cluster start up, with a long chain of "Recovering unflushed segment 0" seen on some brokers. Is it expected to see these after each shutdown/restart?
On Tue, Aug 19, 2014 at 01:19:34AM +0400, Ivan Balashov wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project 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