【问题标题】:Shutdown broker because all log dirs have failed关闭代理,因为所有日志目录都失败了
【发布时间】:2020-02-24 08:27:03
【问题描述】:
[2019-10-29 10:09:36,903] INFO [ReplicaManager broker=0] Broker 0 stopped fetcher for partitions __consumer_offsets-30,__consumer_offsets-8,__consumer_offsets-4,__consumer_offsets-27,__consumer_offsets-7,__consumer_offsets-46,__consumer_offsets-33,__consumer_offsets-23,__consumer_offsets-49,__consumer_offsets-36,__consumer_offsets-42,topic-0,__consumer_offsets-17,__consumer_offsets-48,__consumer_offsets-11,__consumer_offsets-14,__consumer_offsets-20,__consumer_offsets-0,__consumer_offsets-39,__consumer_offsets-45,__consumer_offsets-1,__consumer_offsets-26,__consumer_offsets-29,__consumer_offsets-10 and stopped moving logs for partitions  because they are in the failed log directory C:\tmp\kafka-logs. (kafka.server.ReplicaManager)
[2019-10-29 10:09:36,908] INFO Stopping serving logs in dir C:\tmp\kafka-logs (kafka.log.LogManager)
[2019-10-29 10:09:36,952] ERROR Shutdown broker because all log dirs in C:\tmp\kafka-logs have failed (kafka.log.LogManager)

我也开始了 zookeeper、Kafka 和 producer。但是当我尝试立即使用数据时,Windows 出现了这个错误 命令:.\bin\windows\Kafka-console-consumer.bat --bootstrap-server localhost:9092 --topic topic

【问题讨论】:

  • 当您将log.dirs 更新为不使用/tmp 位置时会发生什么?
  • 检查这是否有帮助 Old post

标签: apache-kafka


【解决方案1】:

我遇到了类似的问题,不得不反复试验。但我最终所做的是禁用其他 JRE 版本,只启用一个。见附图。这似乎解决了我的问题,因为我的代理不再崩溃。

【讨论】:

    猜你喜欢
    • 2019-01-09
    • 2020-07-30
    • 2012-11-30
    • 1970-01-01
    • 2013-03-31
    • 2019-09-09
    • 1970-01-01
    • 2018-04-20
    • 1970-01-01
    相关资源
    最近更新 更多