error[No partition metadata for topic test-1 due to kafka.common.LeaderNotAvailableException]
http://stackoverflow.com/questions/23228222/running-into-leadernotavailableexception-when-using-kafka-0-8-1-with-zookeeper-3
Kafka uses an external coordination framework (by default Zookeeper) to maintain configuration. It seems the configuration is now out-of-sync with the Kafka log data. In this case, I‘d remove affected topic data and related Zookeeper data.
For Test Environment:
-
Stop
Kafka-serverandZookeeper-server -
Remove the data directories of both services, by default they are
/tmp/kafka-logand/tmp/zookeeper. -
Start
Kafka-serverandZookeeper-serveragain - Create a new topic
Now you are able to work with the topic again.
For Production Environment:
As the Kafka topics are stored in different directories, you should remove particular directories. You should also remove /brokers/{broker_id}/topics/{broken_topic} from
Zookeeper by using a Zookeeper client.
Please read Kafka documentation carefully to make sure the configuration structure, before you do anything stupid. Kafka is rolling out a delete topic feature (KAFKA-330), so that the problem can be solved more easily.
郑重声明：本站内容如果来自互联网及其他传播媒体，其版权均属原媒体及文章作者所有。转载目的在于传递更多信息及用于网络分享，并不代表本站赞同其观点和对其真实性负责，也不构成任何其他建议。
