From 2e763de7b640a897a48b2a40a561e677fea61462 Mon Sep 17 00:00:00 2001 From: Matt Bentley Date: Wed, 30 Nov 2016 17:42:31 -0500 Subject: [PATCH] Move rebalcing to be a top level item Signed-off-by: Matt Bentley --- engine/swarm/admin_guide.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/engine/swarm/admin_guide.md b/engine/swarm/admin_guide.md index ff9d95fe60c5..81a0e0f55466 100644 --- a/engine/swarm/admin_guide.md +++ b/engine/swarm/admin_guide.md @@ -22,6 +22,7 @@ This article covers the following swarm administration tasks: * [Troubleshooting a manager node](#troubleshoot-a-manager-node) * [Forcefully removing a node](#force-remove-a-node) * [Recovering from disaster](#recover-from-disaster) +* [Forcing the swarm to rebalance](#forcing-the-swarm-to-rebalance) Refer to [How nodes work](how-swarm-mode-works/nodes.md) for a brief overview of Docker Swarm mode and the difference between manager and @@ -255,7 +256,7 @@ manager node of a single-node swarm. It discards swarm membership information that existed before the loss of the quorum but it retains data necessary to the Swarm such as services, tasks and the list of worker nodes. -### Forcing the swarm to rebalance +## Forcing the swarm to rebalance Generally, you do not need to force the swarm to rebalance its tasks. When you add a new node to a swarm, or a node reconnects to the swarm after a @@ -283,4 +284,4 @@ balance of your service across nodes. See also [`docker service scale`](../reference/commandline/service_scale.md) and -[`docker service ps`](../reference/commandline/service_ps.md). \ No newline at end of file +[`docker service ps`](../reference/commandline/service_ps.md).