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.

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

merged 1 commit into from
Oct 11, 2016

Conversation

mdlinville
Copy link

Fixes #105

@mdlinville
Copy link
Author

@thaJeztah PTAL


If a node becomes unavailable, it cannot communicate with the rest of the swarm.
If access to that node is restored, it will re-join the swarm, but it will
function as a completely new node. In fact, when it first re-joins, its current
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wonder if we should say "as a completely new node" here (as it still has the same node ID, unless it really left the swarm, and re-joined using docker swarm join).

/cc @aaronlehmann any suggestions?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. Let's not say that re-joins the swarm, because according to our terminology, it never really left; it was just unreachable for a period of time. During that time, its workload would have been rescheduled elsewhere.

@mdlinville
Copy link
Author

Thanks for the feedback. I've reworded it a bit. Can y'all review it again?

@aaronlehmann
Copy link
Contributor

I don't see the changes - looks like they haven't been pushed yet.

@mdlinville
Copy link
Author

Oops, you are right! Should be pushed now.

@aaronlehmann
Copy link
Contributor

LGTM

@mdlinville mdlinville merged commit 232043c into docker:master Oct 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants