-
-
Notifications
You must be signed in to change notification settings - Fork 724
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
top-level Client function to shutdown workers #600
Comments
+1. I'd like to cleanly shutdown my cluster so the Nanny process doesn't respawn the worker. |
Also, can't seem to close scheduler so it exits the CLI-launched scheduler gracefully. I tried
Which seems to close things, but the process hangs around. |
@mrocklin Confirming there's still no way to do this except
? |
Ah no, this might suffice: #1876 |
@adamklein does the |
Closing due to lack of activity. Feel free to re-open if folks would like to continue |
If I have remotely launched workers with a nanny process I can simply use
client.restart()
to dump the cluster. However aWorker
(say launched via a resource manager or some such), can right now be cleanly terminated via:Client.shutdown()
does not do this (despite it seems that the doc-string indicates it.So maybe add a method
Client.shutdown_workers()
?The text was updated successfully, but these errors were encountered: