Kafka, mail # user - Re: Getting LeaderNotAvailableException in console producer after increasing partitions from 4 to 16. - 2013-08-27, 16:52
 Search Hadoop and all its subprojects:

Switch to Threaded View
Copy link to this message
-
Re: Getting LeaderNotAvailableException in console producer after increasing partitions from 4 to 16.
As Guozhang said, your producer might give up sooner than the leader
election completes for the new topic. To confirm if your producer gave up
too soon, you can run the state change log merge tool for this topic and
see when the leader election finished for all partitions

./bin/kafka-run-class.sh kafka.tools.StateChangeLogMerger --logs <location
to all state change logs> --topic <topic>

Note that this tool requires you to give the state change logs for all
brokers in the cluster.
Thanks,
Neha
On Tue, Aug 27, 2013 at 9:45 AM, Guozhang Wang <[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