Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement some form of deletion policy for Spark applications #155

Open
razvan opened this issue Oct 7, 2022 · 0 comments
Open

Implement some form of deletion policy for Spark applications #155

razvan opened this issue Oct 7, 2022 · 0 comments

Comments

@razvan
Copy link
Member

razvan commented Oct 7, 2022

Description

SparkApplications own all resources created by spark-submit, including the driver Pod. Since applications are created by the user, the dependents remain present in the cluster long after the application is finished.

To clean up these (stale) resources, we propose implementing some form of deletion policy for the SparkApplication it's self. Possible policies could be:

  • Never
  • Always
  • AlwaysOnSuccess
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@razvan