Brokers may have temporary problems catching up with the leaders. So I
would not worry about it if it happens only once a while and goes away.
Occasionally we have seen under replicated topics for long time, which
might be caused by ZooKeeper session problem as indicated by such log
messages:
[info] I wrote this conflicted ephemeral node [{"jmx_port":-1,"timestamp":"
1418688028517","host":"ec2-54-75-33-226.eu-west-1.compute.amazonaws.com
","version":1,"port":7101}] at /brokers/ids/0 a while back in a different
session, hence I will backoff for this node to be deleted by Zookeeper and
retry
Typically restarting the Kafka process on such brokers will fix the problem.
On Mon, Dec 29, 2014 at 12:49 PM, Gene Robichaux <gene.robich...@match.com>
wrote:
> My team is new to Kafka so any help is appreciated.
>
> We have a situation where we have 3 under replicated topics. What is the
> best way to correct this?
>
> # bin/kafka-topics.sh --describe --under-replicated-partitions --zookeeper
> ServerName:2181
> Topic: DA_DbExceptionLog Partition: 8 Leader: 2
> Replicas: 3,2,4 Isr: 2,3
> Topic: DA_DebugLog Partition: 12 Leader: 1 Replicas:
> 3,1,2 Isr: 1,2
> Topic: EC_Interaction Partition: 8 Leader: 2 Replicas:
> 3,2,4 Isr: 2,3
>
> Gene Robichaux
> Manager, Database Operations
> Match.com
> 8300 Douglas Avenue I Suite 800 I Dallas, TX 75225
>
>
