ZooKeeper znode controller: release finalizer without connecting when the parent is deleting
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 68/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- kubernetes, rust
调研方向
从 finalizer::Event::Cleanup 分支开始，跟踪它如何处理带有 deletionTimestamp 的被引用 ZookeeperCluster。检查 ensure_znode_missing 清理路径，以及暴露出卡在 Terminating 状态的 namespace 的集成测试。完成的标准是删除操作跳过 ZooKeeper 连接，并在没有数分钟 backoff 的情况下释放 finalizer。
由索引模型根据 Issue 内容生成。
描述
Problem
In some scenarios, the ZookeeperZnode finalizer (zookeeper.stackable.tech/znode) can take around 130–150s to release. That's what sometimes leaves namespaces stuck in Terminating in our integration tests.
This can happen when the operator tries connection to Zookeeper to delete the node, while ZooKeeper is being torn down, the delete/cleanup path (ensure_znode_missing) runs its errors through controller-runtime's exponential backoff, and that's where the multi-minute stall comes from.
Mechanism
- znode cleanup (
ensure_znode_missing) tries to connect to the ZK service and gets Connection refused — the ZK pods/endpoints are already gone — so the reconcile errors out. - The
ZookeeperClusterCR then drops out of the watch cache. At this point the finalizer's fast path (cluster doesn't exist → assume the znode is gone → drop the finalizer without connecting) would kick in, but the failed reconcile is already sitting in exponential backoff. - ~139s gap: nothing re-runs, even though the fast-path condition is now true.
- Backoff finally expires, the reconcile re-runs, the fast path fires, the finalizer is removed, and the namespace deletes.
So it comes down to queue ordering under load. If cleanup runs after the CR leaves the store, it's instant if it runs before, it errors, hits backoff, and takes 130s+.
Fix
In the finalizer::Event::Cleanup arm: if the referenced ZookeeperCluster has a deletionTimestamp, drop the finalizer straight away without connecting to ZK. Retrying an unreachable server makes sense on the create path; on the delete path it shouldn't be allowed to block teardown.
- 主要语言
- Rust
- 星标
- 37
- 派生
- 12
- 平均合并
- 21 小时
- 30 天内合并 PR
- 9
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
stackabletech/zookeeper-operator 的其他 Issue
-
难度 5/5 一周以上 新手友好度 25/100
stackabletech/zookeeper-operator#959 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 35/100
-
type/bug
难度 4/5 3-5 天 新手友好度 30/100
-
type/bug
难度 4/5 3-5 天 新手友好度 35/100
-
难度 4/5 3-5 天 新手友好度 30/100
查看 stackabletech/zookeeper-operator 的全部 Issue
相似的 Issue
-
[Bug] Completion info popup (.cm-completionInfo) ignores the configured editor font可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭bug user-priority/P2
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
rescript-lang/rescript#8765 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
nautechsystems/nautilus_trader#5287 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 62/100
farion1231/cc-switch#8072 ·
维护者通常 1 天内回复
-
Python 3.15 support可能已有人在做 @amnesiaof 今天认领。 未关闭L: python L: python:uv
难度 2/5 1-3 小时 新手友好度 72/100
dependabot/dependabot-core#16524 · 1 条评论 ·
维护者通常 1 天内回复