KRaft: a new controller can bootstrap against itself and never join the quorum
维护者通常 1 天内回复
评估
这个 Issue 还没有评估数据。
描述
Description
A controller that starts without metadata (a new pod, e.g. after scaling up a controller role group) finds the quorum leader through controller.quorum.bootstrap.servers. Outside Kerberos, that list has one entry per controller role group: the role group's headless Service. That Service sets publishNotReadyAddresses: true, so the name also resolves to the starting pod's own IP.
Kafka treats each entry in controller.quorum.bootstrap.servers as one bootstrap node and resolves its name when it connects. If the starting pod's lookup returns its own IP, the connection succeeds, so Kafka never tries another address. The pod asks itself for the leader, gets no answer, and repeats this forever.
This is a race in the quorum management added in #1010.
Symptoms
- The new controller stays in Raft state
unattached(epoch 0) and never becomes an observer. The quorum's replication status doesn't list it at all. - Its
quorum-managersidecar logsLocal Raft state is 'unattached', nothing to doindefinitely, so it never callsadd-controller. - The
kafkacontainer never becomes ready, and the StatefulSet rollout stalls. Because the StatefulSet usesOrderedReady, later replicas are not created either. - The pod's only connections on the controller port go to its own IP.
- Deleting the pod usually clears it: the replacement resolves another IP and joins normally.
- 主要语言
- Rust
- 星标
- 31
- 派生
- 9
- 平均合并
- 4 天 5 小时
- 30 天内合并 PR
- 14
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
stackabletech/kafka-operator 的其他 Issue
-
Use mTLS instead of Kerberos for KRaft inter-node traffic可能已有人在做 @razvan 于 1 天前认领。 未关闭type/internal-improvement
stackabletech/kafka-operator#1066 · 已指派 1 人 ·
维护者通常 1 天内回复
-
KRaft: adding a controller role group can bootstrap a second quorum可能已有人在做 @razvan 于 1 天前认领。 未关闭type/bug
stackabletech/kafka-operator#1060 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 30/100
stackabletech/kafka-operator#1059 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 35/100
stackabletech/kafka-operator#1058 ·
维护者通常 1 天内回复
-
type/bug
难度 5/5 一周以上 新手友好度 35/100
stackabletech/kafka-operator#955 · 1 条评论 ·
维护者通常 1 天内回复
查看 stackabletech/kafka-operator 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
storytold/photocraft#14822 ·
维护者通常 1 天内回复
-
bug css
难度 2/5 1-3 小时 新手友好度 66/100
dginev/latexml-oxide#853 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 2 天内回复
-
[Bug] export_build_environment admits its output directory only after the export ran in the build computer可能已有人在做 @viniciusdsandrade 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复