Configured broker.id 2 doesn‘t match stored broker.id 3 in meta.properties
完整報錯:
(Python3.6) appleyuchi@Laptop:config$ [2020-12-17 14:09:03,904] ERROR Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
kafka.common.InconsistentBrokerIdException: Configured broker.id 2 doesn't match stored broker.id 3 in meta.properties. If you moved your data, make sure your configured broker.id matches. If you intend to create a new broker, you should remove all data in your data directories (log.dirs).
? ? ? ? at kafka.server.KafkaServer.getOrGenerateBrokerId(KafkaServer.scala:767)
? ? ? ? at kafka.server.KafkaServer.startup(KafkaServer.scala:226)
? ? ? ? at kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:44)
? ? ? ? at kafka.Kafka$.main(Kafka.scala:82)
? ? ? ? at kafka.Kafka.main(Kafka.scala)
?
原因①:
在啟動過kafka之后,已經(jīng)在$KAFKA/logs/meta.properties中生成了broker.id
在修改了該節(jié)點(diǎn)的$KAFKA/config/server.properties中的broker.id以后
然后再次啟動,就會導(dǎo)致上述問題.
因為此時$KAFKA/config/server.properties中的broker.id與$$KAFKA/logs/meta.properties中的broker.id發(fā)生不一致了.
原因②:
$KAFKA/config/server.properties中被改掉了
那么啟動kafka以后就會在最新的log.dirs路徑中與該路徑原有的meta.properties中的broker.id產(chǎn)生沖突
?
解決方案:
刪除$KAFKA/logs整個文件夾,然後重啟kafka集群即可
總結(jié)
以上是生活随笔為你收集整理的Configured broker.id 2 doesn‘t match stored broker.id 3 in meta.properties的全部內(nèi)容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: 腾讯新闻APP怎么把朗读改为男声(腾讯视
- 下一篇: 玄元剑仙绝学有什么用