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 25, 2015 at 5:46 PM, ZhuGe <t...@outlook.com> 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 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 > > 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 <t...@outlook.com> 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. 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_rtdc_flumesinks PartitionCount:12 > > > ReplicationFactor:3 Configs: Topic: wx_rtdc_flumesinks > > > Partition: 0 Leader: 2 Replicas: 1,2,0 Isr: 2,0 Topic: > > > wx_rtdc_flumesinks Partition: 1 Leader: 2 Replicas: > 2,0,1 > > > Isr: 2,0 Topic: wx_rtdc_flumesinks Partition: 2 > Leader: 0 > > > Replicas: 0,1,2 Isr: 0,2 Topic: wx_rtdc_flumesinks > > > Partition: 3 Leader: 0 Replicas: 1,0,2 Isr: 0,2 Topic: > > > wx_rtdc_flumesinks Partition: 4 Leader: 2 Replicas: > 2,1,0 > > > Isr: 2,0 Topic: wx_rtdc_flumesinks Partition: 5 > Leader: 0 > > > Replicas: 0,2,1 Isr: 0,2 Topic: wx_rtdc_flumesinks > > > Partition: 6 Leader: 2 Replicas: 1,2,0 Isr: 2,0 Topic: > > > wx_rtdc_flumesinks Partition: 7 Leader: 2 Replicas: > 2,0,1 > > > Isr: 2,0 Topic: wx_rtdc_flumesinks Partition: 8 > Leader: 0 > > > Replicas: 0,1,2 Isr: 0,2 Topic: wx_rtdc_flumesinks > > > Partition: 9 Leader: 0 Replicas: 1,0,2 Isr: 0,2 Topic: > > > wx_rtdc_flumesinks Partition: 10 Leader: 2 Replicas: > 2,1,0 > > > Isr: 2,0 Topic: wx_rtdc_flumesinks Partition: 11 > Leader: 0 > > > Replicas: 0,2,1 Isr: 0,2 > > > It seems the broker is out of synchronize with other brokers. and > nothing > > > changed after i run preferred replication leader election tool. i > think it > > > is because the preferred replication is not in Isr, which is described > in > > > the wiki of replication tool. > > > I want to know how to synchronize the replications of 3 brokers so that > > > the broker 1 could work properly.any help would be appreciated. > > > ____________________________________________________________ > > > High School Yearbooks > > > View Class Yearbooks Online Free. Reminisce & Buy a Reprint Today! > > > > http://thirdpartyoffers.netzero.net/TGL3255/54ed7fb69616f7fb61578mp03duc > >
