Kafka, mail # user - Re: Fatal issue (was RE: 0.8 throwing exception "Failed to find leader" and high-level consumer fails to make progress_ - 2013-07-31, 04:17
Solr & Elasticsearch trainings in New York & San Francisco [more info][hide]
 Search Hadoop and all its subprojects:

Switch to Threaded View
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_
Hmm, that's a good theory. My understanding is that you have one thread
that first shuts down the consumer connector and then creates new streams
on the same connector. Is that right? If so, I don't think the race
condition can happen. When we shutdown the consumer connector, it waits
until the leaderFinder thread is stopped. So, if the leaderFinder thread is
still being started, shutdown will block.

Thanks,

Jun
On Tue, Jul 30, 2013 at 9:34 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