has_what(self, workers=None, **kwargs)

This returns the keys of the data that are held in each worker's memory.

Parameters

workers : list (optional)

A list of worker addresses, defaults to all

Which keys are held by which workers

See Also

Client.nthreads

Client.processing

Client.who_has

Examples

This example is valid syntax, but we were not able to check execution

>>> x, y, z = c.map(inc, [1, 2, 3])  # doctest: +SKIP
... wait([x, y, z])  # doctest: +SKIP
... c.has_what()  # doctest: +SKIP
{'192.168.1.141:46784': ['inc-1c8dd6be1c21646c71f76c16d09304ea',
                         'inc-fd65c238a7ea60f6a01bf4c8a5fcf44b',
                         'inc-1e297fc27658d7b67b3a758f16bcf47a']}

See :

Back References

The following pages refer to to this document either explicitly or contain code examples using this.

distributed.client.Client.processing distributed.client.Client.nthreads distributed.client.Client.who_has

Local connectivity graph

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

---

File: /distributed/client.py#3236
type: <class 'function'>
Commit: