Allow defining a time to live for finished SparkApplication driver pods
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- kubernetes, rust, spark
- Domain
- infrastructure
Research direction
Start by reading the SparkApplication specification and the driver/executor pod cleanup flow. Trace how finished driver pods are deleted and how spark.kubernetes.executor.deleteOnTermination is handled. Done means a driver.ttlSecondsAfterFinished field supports delayed cleanup, preserves executors for the same period unless explicitly disabled, and keeps the current immediate-delete default.
Written by the indexing model from the issue text.
Description
While looking into why the sensor in https://docs.stackable.tech/home/stable/airflow/usage-guide/applying-custom-resources/#_dag_code is not able to pull driver logs, I noticed that there is no way to stop driver / executor pods from being immediately deleted after the spark application finishes.
There is a sparkConf value for executors (spark.kubernetes.executor.deleteOnTermination - not considered by the operator and which cannot be acted upon by spark itself because the driver immediately terminates) but nothing comparable for drivers. We could define a new field:
spec:
driver:
ttlSecondsAfterFinished: 600 # default 0 = delete immediately, as today
To enable to sensor use case or allow better debugging. When set to a value > 0, the executor pods should also be kept around as long as deleteOnTermination is not set to false.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 4
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 15
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/spark-k8s-operator
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
type/bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
type/bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
type/bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
stackabletech/spark-k8s-operator#730 · 6 comments ·
-
customer-request type/bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
stackabletech/spark-k8s-operator#701 · 1 comment ·
All issues in stackabletech/spark-k8s-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TheLarkInn/aipm#2413 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
alexgorbatchev/simple-ptt#15 ·
-
tooling
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
todo:ticket
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
taikoxyz/taiko-mono#22168 · 1 comment ·