Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> Fatal issue (was RE: 0.8 throwing exception "Failed to find leader" and high-level consumer fails to make progress_


Copy link to this message
-
Re: Fatal issue (was RE: 0.8 throwing exception "Failed to find leader" and high-level consumer fails to make progress_
Ok. So, it seems that the issue is there are lots of rebalances in the
consumer. How long did you set the zk session expiration time? A typical
reason for many rebalances is the consumer side GC. If so, you will see
Zookeeper session expirations in the consumer log (grep for Expired).
Occasional rebalances are fine. Too many rebalances can slow down the
consumption and one will need to tune the java GC setting.

Thanks,

Jun
On Sat, Jul 27, 2013 at 9:33 AM, Hargett, Phil <
[EMAIL PROTECTED]> wrote:
 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB