Closed consideRatio closed 9 months ago
I would only do this if there is a clear benefit to disabling the nanny or some problem that it is causing. For example on some HPC systems the nanny causes problems because each job can only start one process.
In https://distributed.dask.org/en/stable/killed.html#killed-by-nanny its documented that it could make sense to disable the nanny. I wonder if it makes sense for the dask-gateway helm chart to do that by default or not but I don't know the details well enough to determine this.
I know that a k8s pod running a container has a
restartPolicy
defaulting toAlways
, meaning that a container that crashes will restart by default. Is that making the nanny unnessecary?