Do you see broker 1 being deleted in the controller log?
Thanks,
Jun
On Fri, Feb 27, 2015 at 5:25 PM, ZhuGe wrote:
> Thanks for the reply.I confirmed that broker 1 is registered in the zk.
>
>
> > Date: Fri, 27 Feb 2015 09:27:52 -0800
> > Subject: Re: broker restart
Thanks for the reply.I confirmed that broker 1 is registered in the zk.
> Date: Fri, 27 Feb 2015 09:27:52 -0800
> Subject: Re: broker restart problems
> From: j...@confluent.io
> To: users@kafka.apache.org
>
> The log seems to suggest that broker 1 is offline. Is broker 1 reg
gt; kafka.controller.ReplicaStateMachine$BrokerChangeListener.handleChildChange(ReplicaStateMachine.scala:327)
> at org.I0Itec.zkclient.ZkClient$7.run(ZkClient.java:568)at
> org.I0Itec.zkclient.ZkEventThread.run(ZkEventThread.java:71)
>
> Thank you very much
> > Fro
.handleChildChange(ReplicaStateMachine.scala:327)
at org.I0Itec.zkclient.ZkClient$7.run(ZkClient.java:568)at
org.I0Itec.zkclient.ZkEventThread.run(ZkEventThread.java:71)
Thank you very much
> From: t...@outlook.com
> To: users@kafka.apache.org
> Subject: RE: broker restart problems
Thanks> Date: Thu, 26 Feb 2015 13:11:24 -0800
> Subject: Re: broker restart problems
> From: j...@confluent.io
> To: users@kafka.apache.org
>
> Right, you need to look into why the restarted broker is not sync-ed up.
> Any error in the controller and state-change log? Also, w
be false.
> BTW, it this command means periodically invoking 'preferred replica leader
> election tool'?and how should i solve the "out of syn" problem of the
> broker?
> > Date: Wed, 25 Feb 2015 16:09:42 -0800
> > Subject: Re: broker restart problems
we did not have this setting in the property file, so it should be false. BTW,
it this command means periodically invoking 'preferred replica leader election
tool'?and how should i solve the "out of syn" problem of the broker?
> Date: Wed, 25 Feb 2015 16:09:42 -0800
> S
Do you have the property auto.leader.rebalance.enable=true set in brokers?
Thanks
-Zakee
On Tue, Feb 24, 2015 at 11:47 PM, ZhuGe wrote:
> Hi all:We have a cluster of 3 brokers(id : 0,1,2). We restart(simply use
> stop.sh and start.sh in bin directory) broker 1. The broker started
> successfully
Hi all:We have a cluster of 3 brokers(id : 0,1,2). We restart(simply use
stop.sh and start.sh in bin directory) broker 1. The broker started
successfully. However, all the partitions' leader moved to other brokers and no
data were written into broker 2. This is the status of one
topic:Topic:wx_
