Skip to content

Clarify what happens when a failed swarm node recovers #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 11, 2016
Merged

Clarify what happens when a failed swarm node recovers #148

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 11 additions & 0 deletions engine/swarm/admin_guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.