-
Notifications
You must be signed in to change notification settings - Fork 55
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
feat(dask): make dask autoscaler optional #834
Closed
Alputer opened this issue
Sep 20, 2024
· 0 comments
· Fixed by #835, reanahub/reana-server#702, reanahub/reana-workflow-controller#604 or reanahub/reana-commons#474 · May be fixed by #791
Closed
feat(dask): make dask autoscaler optional #834
Alputer opened this issue
Sep 20, 2024
· 0 comments
· Fixed by #835, reanahub/reana-server#702, reanahub/reana-workflow-controller#604 or reanahub/reana-commons#474 · May be fixed by #791
Labels
Comments
Alputer
added a commit
to Alputer/reana
that referenced
this issue
Sep 20, 2024
Alputer
added a commit
to Alputer/reana-workflow-controller
that referenced
this issue
Sep 20, 2024
Alputer
added a commit
to Alputer/reana-server
that referenced
this issue
Sep 20, 2024
This was referenced Sep 20, 2024
Alputer
changed the title
Make dask autoscaler optional
feat(dask): make dask autoscaler optional (#834)
Sep 20, 2024
Alputer
changed the title
feat(dask): make dask autoscaler optional (#834)
feat(dask): make dask autoscaler optional
Nov 4, 2024
Alputer
added a commit
to Alputer/reana
that referenced
this issue
Nov 11, 2024
Alputer
added a commit
to Alputer/reana
that referenced
this issue
Nov 11, 2024
Alputer
added a commit
to Alputer/reana
that referenced
this issue
Nov 11, 2024
Alputer
added a commit
to Alputer/reana-workflow-controller
that referenced
this issue
Nov 11, 2024
Alputer
added a commit
to Alputer/reana-server
that referenced
this issue
Nov 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, all dask workflows are executed with autoscaler. However, while experimenting with several examples, autoscaler behaves sometimes weirdly by scheduling more than the maximum number of workers or schedulers not being able to detect some workers, although restarting of the workers solve the issue. Therefore, it is better to decide if this option is enabled to cluster administrators.
The text was updated successfully, but these errors were encountered: