optimize some descriptions for swarm nodes.md
Signed-off-by: lixiaobing10051267 <li.xiaobing1@zte.com.cn>
This commit is contained in:
parent
bad654b00c
commit
fa52bd5cf8
1 changed files with 2 additions and 2 deletions
|
@ -43,12 +43,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.
|
||||
|
||||
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
|
||||
from the failure of a manager node without downtime.
|
||||
|
||||
* 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.
|
||||
* An `N` manager cluster will tolerate the loss of at most
|
||||
`(N-1)/2` managers.
|
||||
|
|
Loading…
Add table
Reference in a new issue