Parameters

names: List[str] :

Names of the locks to acquire. Choosing the same name allows two disconnected processes to coordinate a lock.

client: Client (optional) :

Client to use for communication with the scheduler. If not given, the default global client will be used.

Distributed Centralized Lock

Examples

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

>>> lock = MultiLock(['x', 'y'])  # doctest: +SKIP
... lock.acquire(timeout=1)  # doctest: +SKIP
... # do things with protected resource 'x' and 'y'
... lock.release()  # doctest: +SKIP

See :

Back References

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

distributed.multi_lock.MultiLock.acquire distributed.multi_lock.MultiLockExtension distributed.multi_lock.MultiLockExtension._request_locks distributed.multi_lock.MultiLock distributed.multi_lock.MultiLockExtension._refain_locks

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/multi_lock.py#142
type: <class 'type'>
Commit: