|
@@ -849,7 +849,7 @@ The lock module is used to serialize access to resources used by clients.
|
|
|
Multiple clients can attempt to acquire a lock but only one can have it at a time.
|
|
Multiple clients can attempt to acquire a lock but only one can have it at a time.
|
|
|
Once the lock is released, the next client waiting for the lock will receive it.
|
|
Once the lock is released, the next client waiting for the lock will receive it.
|
|
|
|
|
|
|
|
-**Warning:** This module is deprecated at v0.4, and will be back later. See [Modules][modules] for more details.
|
|
|
|
|
|
|
+**Warning:** This module is deprecated at v0.4. See [Modules][modules] for more details.
|
|
|
|
|
|
|
|
|
|
|
|
|
### Acquiring a Lock
|
|
### Acquiring a Lock
|
|
@@ -996,7 +996,7 @@ If you specify a field other than `index` or `value` then you'll receive the fol
|
|
|
|
|
|
|
|
The leader module wraps the lock module to provide a simple interface for electing a single leader in a cluster.
|
|
The leader module wraps the lock module to provide a simple interface for electing a single leader in a cluster.
|
|
|
|
|
|
|
|
-**Warning:** This module is deprecated at v0.4, and will be back later. See [Modules][modules] for more details.
|
|
|
|
|
|
|
+**Warning:** This module is deprecated at v0.4. See [Modules][modules] for more details.
|
|
|
[modules]: https://github.com/coreos/etcd/blob/master/Documentation/modules.md
|
|
[modules]: https://github.com/coreos/etcd/blob/master/Documentation/modules.md
|
|
|
|
|
|
|
|
|
|
|