Skip to content
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

backport libnetwork #1704 to 1.13/17.03 branch #1821

Merged
merged 1 commit into from
Jun 25, 2017

Conversation

sanimej
Copy link

@sanimej sanimej commented Jun 25, 2017

When the last task(s) are brought down on a node, network leave event is
also sent. network leave could potentially race with the task delete
events and if happens to complete first the task delete events won't be
sent out resulting in stale entries in the remote nodes. Clean up all
the state from a node for a network when a network leave event is
received from a node.

Signed-off-by: Santhosh Manohar santhosh@docker.com

When the last task(s) are brought down on a node, network leave event is
also sent. network leave could potentially race with the task delete
events and if happens to complete first the task delete events won't be
sent out resulting in stale entries in the remote nodes. Clean up all
the state from a node for a network when a network leave event is
received from a node.

Signed-off-by: Santhosh Manohar <santhosh@docker.com>
@sanimej sanimej changed the title control-plane hardening: cleanup local state on peer leaving a network backport libnetwork #1704 to 1.13/17.03 branch Jun 25, 2017
@fcrisciani
Copy link

LGTM

@sanimej sanimej merged commit 56ef2a2 into moby:release/v0.9 Jun 25, 2017
@andrewhsu
Copy link
Member

This brings in #1704 control-plane hardening: cleanup local state on peer leaving a network

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.

3 participants