SparkApplication CRD improvements

未关闭
  • 哪里不对？
#659 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@razvan 已经在做这个了。

开始于 2026年2月25日。

  • #711 来自 @razvan —— 未关闭

评估

这个 Issue 还没有评估数据。

描述

refinement-needed

Description

The current implementation of the operator uses a Kubernetes Job workload running spark-submit in order to create Spark applications.

While this works fine for most cases, it has several drawbacks that cannot be easily addressed.

The primary reason for these drawbacks is the fact the Job pod adds a level of indirection between the operator and the applications such that the operator loses some control over parts of the resources owned by the application.

This architecture makes it unnecessarily complex to run applications in "client" mode. But this mode has many benefits over the "cluster" mode:

  • It makes application monitoring more robust and reliable.
  • It makes the application life cycle management more robust. This is particularly important for streaming applications.
  • It makes application owned resource cleanup configurable and transparent.

[!NOTE]
In client mode, the driver runs on the same Pod as as the submit command and it requires a headless service where the executors can connect back to the driver. To create this service, the operator needs to know the name of the driver Pod. The operator cannot know the name of this Pod until it creates the Job object at which point it doesn't have control over any other resources (most notably executor Pods). This lack of control can then lead to application startup failures.

Further improvements:

  • Allow users to delete application CRs on condition (always, onSuccess) to free up resources and make app names reusable.

Proposal

Summary: Introduce a new version of the SparkApplication CRD without the spec.job field and that runs in client mode only.

  1. How does it make monitoring more robust?

When the operator is in control of driver and executor pods, it can take all of them in consideration when updating the application status.

Currently only the driver pod is taken into consideration.

  1. How does it make application life cycle more robust?

The operator can recognize failure states of both driver and executors and can act accordingly.

Currently the Job workload resubmits applications without much control from the operator.
In some cases, failure states are not propagated properly from executors to the Job pod, which leaves the application "hanging" in a failure state.

  1. How does it make resource cleanup better?

All resources owned by the application are created by the operator and not by the submit job.
Therefore the operator knows exactly what it needs to clean up and when.

主要语言
Rust
星标
74
派生
5
平均合并
10 小时 42 分钟
30 天内合并 PR
17

环境准备

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

从这里开始

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

stackabletech/spark-k8s-operator 的其他 Issue

查看 stackabletech/spark-k8s-operator 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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