Hello, We are using 0.8.2 kafka version. We are running 5 brokers in the prod cluster. Each topic is having two partitions. We are seeing some issues with some topic partitions.
For some topic partitions leader was set to -1. I am not seeing any errors in the controller and server logs. After server restart leader was set to some topic partitions. Will it be a data loss of that topic partition. Looks like, there is no data loss according to my application metrics but I do not have any server logs to prove it from kafka side. *kafka-topics --zookeeper localhost:2181 --describe --topic click_json* Topic: click_json PartitionCount:2 ReplicationFactor:3 Configs:retention.bytes=42949672960 Topic: click_json Partition: 0 Leader: 4 Replicas: 4,5,1 Isr: 4,1,5 Topic: click_json *Partition: 1 Leader: -1 *Replicas: 5,1,2 *Isr: * *Why leader was set to -1?* *What is the impact in case if leader was set to -1?* *How to recover from this error? Which option would be better --> Restart of broker or choosing leader by running prefer leader election script? FYI, we have set unclean.leader.election.enable to false on 3 machines and unclean.leader.election.enable to true on 2 machines. Thanks in advance!!! ------ Thanks, Raju Bairishetti, www.lazada.com
