From a0f2fd5022113cdf00d77001e7bf70d466b73948 Mon Sep 17 00:00:00 2001 From: lixiaobing10051267 Date: Thu, 11 Aug 2016 19:07:56 +0800 Subject: [PATCH] optimize some descriptions for swarm nodes.md Signed-off-by: lixiaobing10051267 Upstream-commit: fa52bd5cf8f8e40189a0a9ba1bac61bd5ace4a91 Component: engine --- components/engine/docs/swarm/how-swarm-mode-works/nodes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/components/engine/docs/swarm/how-swarm-mode-works/nodes.md b/components/engine/docs/swarm/how-swarm-mode-works/nodes.md index 90f37caaf7..6249937eb4 100644 --- a/components/engine/docs/swarm/how-swarm-mode-works/nodes.md +++ b/components/engine/docs/swarm/how-swarm-mode-works/nodes.md @@ -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.