Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Move rebalcing to be a top level item
Signed-off-by: Matt Bentley <[email protected]>
  • Loading branch information
Matt Bentley committed Nov 30, 2016
commit 2e763de7b640a897a48b2a40a561e677fea61462
5 changes: 3 additions & 2 deletions engine/swarm/admin_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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).
[`docker service ps`](../reference/commandline/service_ps.md).