Kafka, mail # user - Re: Fetch request with correlation id 1171437 from client ReplicaFetcherThread-0-1 on partition [meetme,0] failed due to Leader not local for partition - 2013-06-29, 15:46
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: Fetch request with correlation id 1171437 from client ReplicaFetcherThread-0-1 on partition [meetme,0] failed due to Leader not local for partition
Is that warning transient? If not, take a look at the state-change.log.
This should include all the leaderAndIsr requests. See the leader received
by this broker matches what's determined by the controller (in the
controller.log in the controller broker).

Thanks,

Jun
On Fri, Jun 28, 2013 at 11:26 PM, Vadim Keylis <[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