dependencies: set(TaskState instances)
The data needed by this key to run
dependents: set(TaskState instances)
The keys that use this dependency.
duration: float
Expected duration the a task
priority: tuple
The priority this task given by the scheduler. Determines run order.
state: str
The current state of the task. One of ["waiting", "ready", "executing", "fetch", "memory", "flight", "long-running", "rescheduled", "error"]
who_has: set(worker)
Workers that we believe have this data
coming_from: str
The worker that current task data is coming from if task is in flight
waiting_for_data: set(keys of dependencies)
A dynamic version of dependencies. All dependencies that we still don't have for a particular key.
resource_restrictions: {str: number}
Abstract resources required to run a task
exception: str
The exception caused by running a task if it erred
traceback: str
The exception caused by running a task if it erred
type: type
The type of a particular piece of data
suspicious_count: int
The number of times a dependency has not been where we expected it
startstops: [{startstop}]
Log of transfer, load, and compute times for a task
start_time: float
Time at which task begins running
stop_time: float
Time at which task finishes running
metadata: dict
Metadata related to task. Stored metadata should be msgpack serializable (e.g. int, string, list, dict).
nbytes: int
The size of a particular piece of data
annotations: dict
Task annotations
A named tuple containing the function
, args
, kwargs
and task
associated with this TaskState
instance. This defaults to None
and can remain empty if it is a dependency that this worker will receive from another worker.
Holds volatile state relating to an individual Dask task
The following pages refer to to this document either explicitly or contain code examples using this.
distributed.worker.TaskState
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