Jana Radhakrishnan 7b905d3c63 Purge stale nodes with same prefix and IP ... Since the node name randomization fix, we need to make sure that we purge the old node with the same prefix and same IP from the nodes database if it still present. This causes unnecessary reconnect attempts. Also added a change to avoid unnecessary update of local lamport time and only do it of we are ready to do a push pull on a join. Join should happen only when the node is bootstrapped or when trying to reconnect with a failed node. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>		2016-09-23 14:48:54 -07:00
..
broadcast.go	Recover from transient gossip failures	2016-09-19 15:58:14 -07:00
cluster.go	Purge stale nodes with same prefix and IP	2016-09-23 14:48:54 -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