Enforce resource requirements with c-groups?
Open
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 778
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 3
Description
Currently the dask-worker process runs a nanny that then creates a new process. We currently track things like memory use and kill the process if it exceeds that limit. In systems that support it, we might also consider using linux c-groups. Should we? Or should we say that that is orthogonal?
Contributor guide
Assessment
This issue has not been assessed yet.