Can you check if you replica fetcher thread is still running on broker 1? Also, you may check the public access log on broker 5 to see if there are fetch requests from broker 1.
On 2/28/15, 12:39 AM, "tao xiao" <xiaotao...@gmail.com> wrote: >Thanks Harsha. In my case the replica doesn't catch up at all. the last >log >date is 5 days ago. It seems the failed replica is excluded from >replication list. I am looking for a command that can add the replica back >to the ISR list or force it to start sync-up again > >On Sat, Feb 28, 2015 at 4:27 PM, Harsha <ka...@harsha.io> wrote: > >> you can increase num.replica.fetchers by default its 1 and also try >> increasing replica.fetch.max.bytes >> -Harsha >> >> On Fri, Feb 27, 2015, at 11:15 PM, tao xiao wrote: >> > Hi team, >> > >> > I had a replica node that was shutdown improperly due to no disk space >> > left. I managed to clean up the disk and restarted the replica but the >> > replica since then never caught up the leader shown below >> > >> > Topic:test PartitionCount:1 ReplicationFactor:3 Configs: >> > >> > Topic: test Partition: 0 Leader: 5 Replicas: 1,5,6 Isr: 5,6 >> > >> > broker 1 is the replica that failed before. Is there a way that I can >> > force >> > the replica to catch up the leader? >> > >> > -- >> > Regards, >> > Tao >> > > > >-- >Regards, >Tao
