The nanny spins up Worker processes, watches then, and kills or restarts them as necessary. It is necessary if you want to use the Client.restart
method, or to restart the worker automatically if it gets to the terminate fraction of its memory limit.
The parameters for the Nanny are mostly the same as those for the Worker with exceptions listed below.
Environment variables set at time of Nanny initialization will be ensured to be set in the Worker process as well. This argument allows to overwrite or otherwise set environment variables for the Worker. It is also possible to set environment variables using the option :None:None:`distributed.nanny.environ`. Precedence as follows
Nanny arguments
Existing environment variables
Dask configuration
A process to manage worker processes
The following pages refer to to this document either explicitly or contain code examples using this.
distributed.deploy.spec.SpecCluster
Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.
Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)
SVG is more flexible but power hungry; and does not scale well to 50 + nodes.
All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them