kafka有些分区leader为-1的问题

最新推荐文章于 2025-02-26 10:40:32 发布

L13763338360

最新推荐文章于 2025-02-26 10:40:32 发布

阅读量3.9k

点赞数 2

CC 4.0 BY-SA版权

分类专栏： kafka

本文链接：https://blog.youkuaiyun.com/L13763338360/article/details/105638648

kafka 专栏收录该内容

20 篇文章

订阅专栏

本文介绍当Kafka分区的Leader在Broker关闭时变为-1的异常现象，分析其原因在于Broker关闭时Controller选主失败，提供通过重启Controller所在的Broker解决问题的详细步骤。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

现象

get /kafka/brokers/topics/stock_ticks_test1/partitions/0/state

{"controller_epoch":12,"leader":-1,"version":1,"leader_epoch":5,"isr":[5]}

原因

broker shutdown的时候，partition的leader在此broker上，controller选主没有成功，移除此broker后，对应的partition的leader就被赋值成-1了

解决

重启controller

步骤1：找到controller

进入zk命令行，定位controller在哪个节点

[zk: localhost:2181(CONNECTED) 1] get /kafka/controller
{"version":1,"brokerid":4,"timestamp":"1587371673207"}
cZxid = 0x329f55eb3
ctime = Mon Apr 20 16:34:33 CST 2020
mZxid = 0x329f55eb3
mtime = Mon Apr 20 16:34:33 CST 2020
pZxid = 0x329f55eb3
cversion = 0
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x100bf66c3b90445
dataLength = 54
numChildren = 0

步骤2：重启controller所在broker 4

bin/kafka-server-stop.sh

bin/kafka-server-start.sh -daemon ./config/server.properties

步骤3：重新查看分区信息

get /kafka/brokers/topics/stock_ticks_test1/partitions/0/state
{"controller_epoch":12,"leader":5,"version":1,"leader_epoch":6,"isr":[5]}
cZxid = 0x309da4876
ctime = Mon Nov 25 17:04:20 CST 2019
mZxid = 0x329f54723
mtime = Mon Apr 20 16:32:18 CST 2020
pZxid = 0x309da4876
cversion = 0
dataVersion = 6
aclVersion = 0
ephemeralOwner = 0x0
dataLength = 73
numChildren = 0

已经恢复正常