dask / dask/distributed

Not monitoring the process tree, only the worker proccess

Open
#1,949 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.7k
Forks
778
Avg merge
2h 50m
Merged PRs (30d)
3

Description

When using subprocess, the memory usage is counted by the local scheduling system but not by distributed, this leads to 2 problems:
A) we can't monitor the processes from the Dashboard properly
B) distributed's handling of memory usage isn't brought into effect, and so the worker is killed by the scheduling system in some cases.

Is this intentional?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.