Skip to content

Commit 232043c

Browse files
author
Misty Stanley-Jones
authored
Merge pull request #148 from mstanleyjones/swarm_add_node_clarify
Clarify what happens when a failed swarm node recovers
2 parents 6955815 + 62f4a04 commit 232043c

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

engine/swarm/admin_guide.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -262,3 +262,14 @@ The `--force-new-cluster` flag puts the Docker Engine into swarm mode as a
262262
manager node of a single-node swarm. It discards swarm membership information
263263
that existed before the loss of the quorum but it retains data necessary to the
264264
Swarm such as services, tasks and the list of worker nodes.
265+
266+
### Joining a previously failed node
267+
268+
If a node becomes unavailable, it cannot communicate with the rest of the swarm
269+
and its workload is redistributed among the other nodes.
270+
If access to that node is restored, it will join the swarm automatically, but it
271+
will join with no workload because the containers it was assigned have been
272+
reassigned. The node will only receive new workloads when the swarm is rebalanced.
273+
To force the swarm to be rebalanced, you can
274+
[update](../reference/commandline/service_update/) or
275+
[scale](../reference/commandline/service_scale/) the service.

0 commit comments

Comments
 (0)