beenull/moby
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Merge pull request #25610 from lixiaobing10051267/masterSwarm

Browse source 
optimize some descriptions for swarm nodes.md
(cherry picked from commit 81fca603a4)

Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
This commit is contained in:
Sebastiaan van Stijn 2016-08-11 13:29:47 +02:00 committed by Sven Dowideit
parent 6a7d5dcf08
commit 6e122d9bd5
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/swarm/how-swarm-mode-works/nodes.md
View file

@ -42,12 +42,12 @@ manager. If the manager in a single-manager swarm fails, your services will
continue to run, but you will need to create a new cluster to recover. continue to run, but you will need to create a new cluster to recover.
To take advantage of swarm mode's fault-tolerance features, Docker recommends To take advantage of swarm mode's fault-tolerance features, Docker recommends
you implement an odd number of nodes nodes according to your organization's you implement an odd number of nodes according to your organization's
high-availability requirements. When you have multiple managers you can recover high-availability requirements. When you have multiple managers you can recover
from the failure of a manager node without downtime. from the failure of a manager node without downtime.
* A three-manager swarm tolerates a maximum loss of one manager. * A three-manager swarm tolerates a maximum loss of one manager.
* A five-manager swarm tolerates a maximum simultaneous loss two * A five-manager swarm tolerates a maximum simultaneous loss of two
manager nodes. manager nodes.
* An `N` manager cluster will tolerate the loss of at most * An `N` manager cluster will tolerate the loss of at most
`(N-1)/2` managers. `(N-1)/2` managers.