Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Putting `dask-worker-space` in `/tmp` is unfriendly on shared systems
See original GitHub issueSince d59500ea97c02753eac9d42951d9c4a5d4f17685 (#6658), launching workers can fail on shared systems if someone else happens to be running at the same time (since they will have created /tmp/dask-worker-space and we won’t have write permissions).
A friendlier approach would probably be to use tempfile.mkdtemp to create the directory. This has the disadvantage that if a cluster fails and doesn’t clean up, a new run would not clean out the old lock directory.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:23 (18 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
HPC users commonly use
dask-jobqueue,dask-ssh,dask-mpianddask-gateway. So if we wanted to handle it downstream those would be the places to do it.Holy loss of segregation, Batman! Jokes aside, won’t all the containers share the same user on the host VM?