Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Ignore previous serf user events to avoid wrong fdb programming #1639
When deploying classic swarm with overlay network and using
To illustrate: One container C1 with three worker nodes W1, W2 and W3.
Container interface's mac is built from the IP address.
If W1 goes through a failure and the container gets rescheduled to W2 the results events will be
At this point if W3's daemon is restarted serf replays all the previous events. But they can be delivered out of order to the client. So libnetwork could end up getting the following..
W3 ends up with incorrect forwarding info.
The change is to avoid getting the older events from serf when joining the gossip cluster. Hence for the containers that are already running in the network the miss notification and query mechanism will be used to program the neighbor entry/FDB.
Also added some debugs to help in debugging.
Signed-off-by: Santhosh Manohar email@example.com