Sure thing - https://issues.apache.org/jira/browse/KAFKA-1452
On May 13, 2014, at 8:33 PM, Jun Rao jun...@gmail.com wrote:
Yes, that seems like a real issue. Could you file a jira?
Thanks,
Jun
On Tue, May 13, 2014 at 11:58 AM, Alex Demidko
alexan...@metamarkets.comwrote:
Hi
Hi,
Kafka version is 0.8.1.1. We have three machines: A,B,C. Let’s say there is a
topic with replication 2 and one of it’s partitions - partition 1 is placed on
brokers A and B. If the broker A is already down than for the partition 1 we
have: Leader: B, ISR: [B]. If the current controller is
Hi,
I’m performing a producing load test on two node kafka cluster built from the
last 0.8.1 branch sources. I have topic loadtest with replication factor 2 and
256 partitions. Initially both brokers are in ISR and leadership is balanced.
When in the middle of the load test one broker was
the controller/state-change log?
Thanks,
Jun
On Fri, Apr 18, 2014 at 9:57 AM, Alex Demidko
alexan...@metamarkets.comwrote:
Hi,
I’m performing a producing load test on two node kafka cluster built from
the last 0.8.1 branch sources. I have topic loadtest with replication
factor 2 and 256
, Alex Demidko
alexan...@metamarkets.com
wrote:
These on alive node:
2014-04-17 21:36:29,276 ERROR [ZkClient-EventThread-15]
state.change.logger - Controller 2 epoch 8 encountered error while
electing
leader for partition [loadtest,143] due to: Preferred replica 1
the restart node, did you see any warn/error on
the leader logs?
Guozhang
On Fri, Apr 18, 2014 at 1:58 PM, Alex Demidko alexan...@metamarkets.com
wrote:
Last time saw this exception when tried to use rebalance leadership with
kafka-preferred-replica-election.sh. That's what got in logs
