subscribe_topic(self, topic, handler)

Parameters

topic: str :

The topic name

handler: callable or coroutine function :

A handler called for every received event. The handler must accept a single argument event which is a tuple :None:None:`(timestamp, msg)` where timestamp refers to the clock on the scheduler.

Subscribe to a topic and execute a handler for every received event

See Also

dask.distributed.Client.get_events

dask.distributed.Client.log_event

dask.distributed.Client.unsubscribe_topic

Examples

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

>>> import logging
... logger = logging.getLogger("myLogger")  # Log config not shown
... client.subscribe_topic("topic-name", lambda: logger.info)

See :

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#3609
type: <class 'function'>
Commit: