There is one fetcher per broker, which is responsible for fetching messages in all consumed topics whose leader is on that broker. We have seen a fetcher being killed by a bug in Kafka. Also, if the broker is slow (e.g. due to I/O contention), the fetch rate could also be slower than expected.
Jun On Tue, Dec 24, 2013 at 12:48 PM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
And, I assume the 'minFetchRate' refers to the lowest fetch rate over all the fetchers (1 per broker) that a consumer has. I see....
On Tue, Dec 24, 2013 at 8:58 PM, Jun Rao <[EMAIL PROTECTED]> wrote:
Jason Rosenberg 2013-12-26, 22:13
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