There are also various mbeans you can poke to check the replica fetcher lag but from your description it appears that the fetcher quit for some reason (since you mentioned the topic is 'pretty much' empty)
BTW, the below is only for partition 0 > Do you have state change logs available? You should have a become > follower state transition on 9255216 and a leader state transition at > around the same time on 925537. The server log should also show > 9255216 starting a replica fetcher thread to the leader. > > Do you have request logging available? You can check if the follower > is issuing fetch requests to the leader. Another option is to take a > threaddump on the follower and see if its replica fetcher thread is > alive or not. > > Joel > > On Thu, May 28, 2015 at 11:26:05AM -0700, Dillian Murphey wrote: > > Nothing on this? Someone must surely have a need to add brokers and > > increase the replication factor. I waited a day and I still do not see > > in-sync replicas. > > > > :( > > > > > > > > On Wed, May 27, 2015 at 5:51 PM, Dillian Murphey <crackshotm...@gmail.com> > > wrote: > > > > > Hi Ho, > > > > > > I'm trying to increase my replication factor from 1 to 2. > > > > > > I used the tool > > > > > > kafka-reassign-partitions.sh > > > > > > I see the replica factor change, but my replicas are not syncing up. There > > > is pretty much no data in this topic. Will this replication get triggered > > > at some point?? > > > > > > root@b3b4b5d71b48:/opt/kafka_2.10-0.8.2.1# > > > $KAFKA_HOME/bin/kafka-topics.sh --describe --zookeeper $ZK --topic mytopic > > > Topic:mytopic PartitionCount:2 ReplicationFactor:2 Configs: > > > Topic: mytopic Partition: 0 Leader: 925537 Replicas: 9255216,925537 Isr: > > > 925537 > > > Topic: mytopic Partition: 1 Leader: 9255216 Replicas: 925537,9255216 Isr: > > > 9255216 > > > > > > > > > Thanks for any comments. > > > >
