error[No partition metadata for topic test-1 due to kafka.common.LeaderNotAvailableException]
2014-11-06 11:12
786 查看
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
Remove the data directories of both services, by default they are
Start
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
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.
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-serverand
Zookeeper-server
Remove the data directories of both services, by default they are
/tmp/kafka-logand
/tmp/zookeeper.
Start
Kafka-serverand
Zookeeper-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.
相关文章推荐
- No partition metadata for topic test due to kafka.common.LeaderNotAvailableException
- Kafka:ZK+Kafka+Spark Streaming集群环境搭建(二十六)Structured Streaming:WARN clients.NetworkClient: Error while fetching metadata with correlation id 1 : {my-topic=LEADER_NOT_AVAILABLE}
- 错误[由于kafka.common.LeaderNotAvailableException而导致的主题test-1的分区元数据]
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- Kafka errors NotLeaderForPartitionException, TimeoutException: Batch containing * record(s) expired
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException
- 【问题】kafka.common.KafkaException: fetching topic metadata for topics
- kafka 生产者给消费者发送消息报 class kafka.common.LeaderNotAvailableException