docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #148 from mstanleyjones/swarm_add_node_clarify 

Clarify what happens when a failed swarm node recovers
This commit is contained in:
Misty Stanley-Jones 2016-10-11 16:14:52 -07:00 committed by GitHub
parent 6955815d23 62f4a04e39
commit 232043cfa6
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
engine/swarm/admin_guide.md
View File

@ -262,3 +262,14 @@ The `--force-new-cluster` flag puts the Docker Engine into swarm mode as a
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.
### Joining a previously failed node
If a node becomes unavailable, it cannot communicate with the rest of the swarm
and its workload is redistributed among the other nodes.
If access to that node is restored, it will join the swarm automatically, but it
will join with no workload because the containers it was assigned have been
reassigned. The node will only receive new workloads when the swarm is rebalanced.
To force the swarm to be rebalanced, you can
[update](../reference/commandline/service_update/) or
[scale](../reference/commandline/service_scale/) the service.