moby--moby/libnetwork/networkdb
Jana Radhakrishnan 22c322dded Avoid returning early on agent join failures
When a gossip join failure happens do not return early in the call chain
because a join failure is most likely transient and the retry logic
built in the networkdb is going to retry and succeed. Returning early
makes the initialization of ingress network/sandbox to not happen which
causes a problem even after the gossip join on retry is successful.

Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>
2016-09-27 08:36:10 -07:00
..
broadcast.go Recover from transient gossip failures 2016-09-19 15:58:14 -07:00
cluster.go Avoid returning early on agent join failures 2016-09-27 08:36:10 -07:00
delegate.go Purge stale nodes with same prefix and IP 2016-09-23 14:48:54 -07:00
event_delegate.go Recover from transient gossip failures 2016-09-19 15:58:14 -07:00
message.go Use protobuf in networkdb core messages 2016-05-17 09:18:24 -07:00
networkdb.go Purge stale nodes with same prefix and IP 2016-09-23 14:48:54 -07:00
networkdb.pb.go Recover from transient gossip failures 2016-09-19 15:58:14 -07:00
networkdb.proto Recover from transient gossip failures 2016-09-19 15:58:14 -07:00
networkdb_test.go Add network scoped gossip database 2016-04-08 12:58:09 -07:00
watch.go Add network scoped gossip database 2016-04-08 12:58:09 -07:00