Re: Failed to start preferred replica election

2013-08-21 Thread Jun Rao
Added to the 0.8 documentation. Thanks, Jun On Tue, Aug 20, 2013 at 9:22 AM, Jay Kreps wrote: > Is there any way to channel these many excellent email threads into > documentation improvements :-) > > -Jay > > > On Mon, Aug 19, 2013 at 8:55 PM, Jun Rao wrote: > > > We also have a jmx bean th

Re: Failed to start preferred replica election

2013-08-20 Thread Jay Kreps
Is there any way to channel these many excellent email threads into documentation improvements :-) -Jay On Mon, Aug 19, 2013 at 8:55 PM, Jun Rao wrote: > We also have a jmx bean that tracks the lag in messages per partition in > the follower broker. > > Thanks, > > Jun > > > On Mon, Aug 19, 20

Re: Failed to start preferred replica election

2013-08-19 Thread Jun Rao
We also have a jmx bean that tracks the lag in messages per partition in the follower broker. Thanks, Jun On Mon, Aug 19, 2013 at 1:07 PM, Vadim Keylis wrote: > It does print partitions. I just did not include them in the bug. > > How can I monitor replica resync progress as well as know when

Re: Failed to start preferred replica election

2013-08-19 Thread Neha Narkhede
You can monitor the under replicated partition count through the "kafka.server.UnderReplicatedPartitions" jmx bean on every leader. Another way, which is heavy weight is to run kafka-list-topics, but I would recommend running that only for diagnostic purposes, not for monitoring. Thanks, Neha On

Re: Failed to start preferred replica election

2013-08-19 Thread Vadim Keylis
It does print partitions. I just did not include them in the bug. How can I monitor replica resync progress as well as know when resync process completed using script? That should allow me to better predict when the tool would run successfully. Thanks so much. On Mon, Aug 19, 2013 at 12:59 PM,

Re: Failed to start preferred replica election

2013-08-19 Thread Neha Narkhede
I think the error message can be improved to at least print which partitions it couldn't move the leader for. What could be happening is that the 2 brokers that were down might not have entered the ISR yet. So the tool will not be able to move any leaders to them. You can run kafka-list-topics with

Failed to start preferred replica election

2013-08-19 Thread Vadim Keylis
I have a cluster of 3 kafka servers. Replication factor is 3. Two out of 3 servers were shutdown and traffic was sent to only one server that was up. I brought second host up and it says according to logs that server has started. I ran ./kafka-list-topic.sh --zookeeper Still was showing leaders a