-
-
Notifications
You must be signed in to change notification settings - Fork 719
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
dask-worker not handling KeyboardInterrupt correctly #2788
Comments
I looked into this a bit today. I think there's a bug in distributed/distributed/cli/dask_worker.py Line 376 in da6a01b
gen.coroutine , else any yield within that call stack will immediately exit the handler (tested with yield gen.sleep(0) in the close_all right above that. Anything after the yield gen.sleep(0) isn't run.
But even after fixing that, I'm still seeing a ctrl-c cause a |
Additionally, we might consider having SIGINT call something like the following in order to cleanly move data away: worker.scheduler.close_workers(..., workers=[self.address]) |
According to slurm documentation processes will be sent in order SIGCONT, SIGTERM, then SIGKILL when on a preemptible queue. I'm guessing sigcont as they might already be suspended. So maybe we ant to also trigger this on sigterm. |
FWIW, I don't see this any more.
Closing. |
Connect a
dask-worker
to the scheduler and thenctrl-c
.That should exit cleanly.
This is related to my PR. Will take a look later.
The text was updated successfully, but these errors were encountered: