Skip to content

Running Daemon Processes from Dask Delayed as a Bridge for Non-Supported functions #7047

Answered by omarsumadi
omarsumadi asked this question in Q&A
Discussion options

You must be logged in to vote

Found a potential answer, when I turn off Daemon Process for the client, I can use submit instead of delayed for the function. Until I can set up a cluster, this at least proves that it works and I can move forward.

Most likely, this is due to: https://stackoverflow.com/questions/6974695/python-process-pool-non-daemonic, the fact that concurrent.futures supports non-daemonic workers, although I currently don't know enough about Dask right now to know why the delayed function didn't work.

I'll still be setting up the KubeCluster (out of this scope) with only 1 Worker and larger # of processes to keep it on 1 single worker until someone else can tell you directly that submitting a function …

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by omarsumadi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant