Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Idea: Start ReportingTaskJob only once the NifiCluster is ready

未关闭
#293 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
kubernetes, rust

调研方向

从 rust/operator-binary/src/controller.rs 第277行附近开始,然后比较 Superset 中引用的 readiness 监听模式。确定提出的方法中哪一种属于范围之内—等待 NifiCluster 就绪、暂停 Job,或将其替换为 HTTP 请求—并验证 reporting 任务在集群就绪之前不再进入正常的 CrashLoopBackOff。

由索引模型根据 Issue 内容生成。

描述

There is a reporting task started immediately: https://github.com/stackabletech/nifi-operator/blob/db33e5e32c55975369e15a063ae21ef728498c2c/rust/operator-binary/src/controller.rs#L277

I want to suggest to follow a pattern we've implemented in Superset: Add a status to the NifiCluster and let the operator listen to it. Only start the job once the cluster is ready.

At the moment the job is started and remains in a CrashLoopBackOff, until the Cluster is ready. This doens't look good and can also cover up actual problems with the job (because this CrashLoopBackoff is 'normal' for us). It would also make the task finish quicker, because at the moment once the cluster is ready, the task is still in a retry-waiting-period. Only once this has passed the job finishes. This can easily save 30 seconds of time.

Edit: since k8s 1.24 Jobs can be started in the suspended state, so the Job object could already be created, but only started once the cluster is up.

Edit: Alternatively the Operator could do the HTTP request, and we could drop the Job altogether

主要语言
Rust
星标
48
派生
12
平均合并
11 小时 26 分钟
30 天内合并 PR
10

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

stackabletech/nifi-operator 的其他 Issue

查看 stackabletech/nifi-operator 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。