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_
ubject: Re: broker restart problems
> From: kzak...@netzero.net
> To: users@kafka.apache.org
>
> 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
hat version of
> Kafka are you on?
>
> Thanks,
>
> Jun
>
> On Wed, Feb 25, 2015 at 5:46 PM, ZhuGe wrote:
>
> > we did not have this setting in the property file, so it should be false.
> > BTW, it this command means periodically invoking 'preferred replica
a.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, what version of
> > Kafka are you on?
> >
> > Thanks,
> >
> > Jun
> >
> > On Wed, Feb 2
istered
> properly in ZK? You can find this out by reading the broker registration
> path (
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+data+structures+in+Zookeeper)
> from ZK.
>
> Thanks,
>
> Jun
>
> On Thu, Feb 26, 2015 at 10:31 PM, ZhuGe wrote:
&g
