-
-
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
Improve memory available detection #1712
Comments
You can solve this manually by telling dask workers to limit their memory usage with To make this more automatic is there a nice way to get the cgroups memory limit from python with a library like psutil? |
I'm looking for it! |
Any update here @asyd ? |
Hi @mrocklin, what do you think about asyd@e6f1883? |
Interesting. Is this accurate for all linux distributions, or do some systems behave differently? |
Since it's a Linux kernel feature it should work on every linux distributions. However, while this workaround will work on my use case (worker runs inside a docker container) I need to improve it to check if the worker runs on root cgroup or a subone by checking |
In
distributed/distributed/worker.py
Line 63 in 5ef9c80
However, in the case of the worker is launched in a cgroup with a memory limitation (memory.limit_in_bytes) the value returned by psutil is the amount of the host, not the amount available in the cgroups, there fore the worker try to use more memory than it can and the linux kernel kill it.
The text was updated successfully, but these errors were encountered: