luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Merge pull request #1601 from bensojona/b-semaphore-typo 

Fix semaphore typo
This commit is contained in:
Ryan Breen 2016-01-13 20:15:00 -05:00
parent db9c418630 d79139760a
commit 0bc021aad2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/docs/guides/semaphore.html.markdown
View File

@ -28,7 +28,7 @@ reading. Actual values returned from the API will not be formatted.
Let's imagine we have a set of nodes who are attempting to acquire a slot in the
semaphore. All nodes that are participating should agree on three decisions: the
prefix in the Key/Value store used to coordinate, a single key to use as a lock,
prefix in the Key/Value store used to coordinate, a single key to use as a lock,
and a limit on the number of slot holders.
For the prefix we will be using for coordination, a good pattern is simply:
@ -73,7 +73,7 @@ The `<session>` value is the ID returned by the call to
to Consul but can be useful for human operators.
The call will either return `true` or `false`. If `true`, the contender entry has been
created. If `false`, the contender node was not created; it'slikely that this indicates
created. If `false`, the contender node was not created; it's likely that this indicates
a session invalidation.
The next step is to use a single key to coordinate which holders are currently