KRaft: adding a controller role group can bootstrap a second quorum
维护者通常 1 天内回复
评估
这个 Issue 还没有评估数据。
描述
Description
In KRaft mode, exactly one controller formats its storage with --standalone and bootstraps the metadata quorum. All other controllers join it later through the quorum-manager
sidecar. This was introduced in #1010, which is not released yet.
The operator picks the bootstrap controller as the one with the lowest node.id in the current spec. Node IDs come from a hash of the role group name, so a controller role
group added later can get lower node IDs than the existing ones. Its first pod starts with an empty volume, formats with --standalone, and becomes the leader of a second,
single-voter quorum under the same cluster ID.
This is not an edge case: any second controller role group added next to it triggers the bug.
Impact
- The new controller never joins the real quorum and keeps its own metadata log under the same cluster ID.
- Nothing in the cluster status shows the problem. The KafkaCluster stays
Available, and the new controller'squorum-managersees itself as leader and does nothing. - Brokers that are already connected stay on the original quorum, so clients keep working. If the original controller role group is removed later, the brokers crash-loop.
- As a side effect, adding such a role group changes the start command of every existing controller, which restarts all of them.
Steps to reproduce
- Create a KRaft KafkaCluster with a
defaultcontroller role group (3 replicas) and a broker role group. - Add a controller role group named
extrawith 1 replica. - Run
kafka-metadata-quorum.sh describe --replicationagainstextra-0. It reports a single-voter quorum led by itself, not the original quorum with 4 voters.
Known limitations (out of scope)
- If the status is lost, the operator chooses the bootstrap controller again from the current spec.
- 主要语言
- 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: a new controller can bootstrap against itself and never join the quorum可能已有人在做 @razvan 于 1 天前认领。 未关闭type/bug
stackabletech/kafka-operator#1062 · 已指派 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 天内回复