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.

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

Clean up resources if dask workflow fails #829

Closed
Alputer opened this issue Sep 6, 2024 · 1 comment
Closed

Clean up resources if dask workflow fails #829

Alputer opened this issue Sep 6, 2024 · 1 comment
Assignees

Comments

@Alputer
Copy link
Member

Alputer commented Sep 6, 2024

Currently, dask resources are cleaned up only if the workflow is successfully completed. We also need to clean them up even if the workflow is not successfully finished.
Kubernetes resources to be cleaned:

  1. Dask cluster
  2. Ingress (used for dask dashboard)
  3. Traefik Middleware (used for dask dashboard)
@Alputer Alputer self-assigned this Sep 6, 2024
@Alputer Alputer added this to Dask Sep 6, 2024
@Alputer Alputer moved this to Ready for work in Dask Sep 6, 2024
@Alputer
Copy link
Member Author

Alputer commented Sep 20, 2024

This issue is already included in the first set of dask integration pr set whose links are given below. Therefore closing the issue.

#821
reanahub/reana-server#701
reanahub/reana-workflow-controller#600
reanahub/reana-job-controller#464
reanahub/reana-commons#467

@Alputer Alputer closed this as completed Sep 20, 2024
@github-project-automation github-project-automation bot moved this from Ready for work to Done in Dask Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

1 participant