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

Application driver Pod is not terminated when Spark is OOMKilled

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

维护者通常 1 天内回复

@razvan 已经在做这个了。

开始于 2026年10月2日。

评估

这个 Issue 还没有评估数据。

描述

type/bug
Affected Stackable version

all

Affected Apache Spark-on-Kubernetes version

No response

Current and expected behavior

When a Spark driver is OOMKilled, the Pod doesn't terminate.

The vector container keeps running even after the Spark process is gone because no Vector shutdown file is generated. This container then prevents the Pod from being terminated.

A shutdown file for vector cannot be generated in this case because SIGKILL cannot be trapped.

A workaround for this problem is to use a livenessProbe on the vector container that connects to the driver's communication port (7078 by default).

Possible solution

A more robust and elegant solution is to turn the vector container into a native sidecar container.

Then Vector would be terminated whenever the main container is terminated. To still give it time collect any remainnig log files, a preStop hook can be used instead of the existing STACKABLE_POST_HOOK.

This solution is a breaking change for anyone using podOverrides to change the vector container. This needs to be documented in the changelog and the release notes.

This change requires Kubernetes >1.33 (which SDP doesn't officially support anymore) but there might still be users running it.

Additional context

No response

Environment

No response

Would you like to work on fixing this bug?

yes

主要语言
Rust
星标
73
派生
5
平均合并
11 小时 13 分钟
30 天内合并 PR
13

环境准备

  • 没有 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 摘要。