Trouble shutting down local distributed client/displaying it afterwards
See original GitHub issueAppears the running Client.close
consistently runs into some sort of hang up. Also it use to be the case that Client._repr_html_
worked on a Client
object after it was closed. However that is no longer the case since Client.scheduler
is now None
. Example of this behavior in the Gist’d Jupyter Notebook linked below along with the environment used to reproduce it. This happens in Distributed 1.21.8, but not in Distributed 1.21.6.
ref: https://gist.github.com/jakirkham/b9c75e2f7fabdee5f19db8cc3bff0d9e
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Error closing a local cluster when client still running #6087
When a local cluster (using processes) shuts down, a ton of errors are now spewed about scheduling new futures after shutdown.
Read more >What is the "right" way to close a Dask LocalCluster?
Expanding on skibee's answer, here is a pattern I use. It sets up a temporary LocalCluster and then shuts it down.
Read more >API — Dask.distributed 2022.12.1 documentation
Thread-local, Task-local context manager that causes the Client.current class method to return self. ... Shut down the connected scheduler and workers.
Read more >Troubleshooting Problems with MSDTC - BizTalk Server
Reinstalling MSDTC may require a reboot of the computer. To ensure that the Distributed Transaction Coordinator service works correctly, reboot ...
Read more >Starting Up and Shutting Down Your System | Geode Docs
Use the appropriate mechanism to shut down any Geode-connected client applications that are running in the cluster. · Shut down any cache servers....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, I think that this started appearing when Tornado switched to Asyncio. We don’t currently have a good way around it. I spent a long while trying to track this down. In the end the solution was to just ignore this if we’re also shutting down the Python process, so in the common case for users it doesn’t show up.
I agree that it’s an issue. I would love to see it resolved.
On Mon, May 7, 2018 at 3:56 PM, jakirkham notifications@github.com wrote:
Went ahead and put it in a new issue ( https://github.com/dask/distributed/issues/1969 ) with a clearer description. Please feel free to add anything else relevant there.