Jana Radhakrishnan 060aa49a70 Fix gossip network event overwriting self ... When a node joins a network it sends out a gossip event before it updates it's own in-memory state. This can create a race where the node gets the event back from a remote node before we update in-memory state and we treat that as latest state. To avoid this race, always generate the gossip after updating local state. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>		2016-04-25 09:47:36 -07:00
..
broadcast.go	Add network scoped gossip database	2016-04-08 12:58:09 -07:00
cluster.go	Fix gossip network event overwriting self	2016-04-25 09:47:36 -07:00
delegate.go	Add network scoped gossip database	2016-04-08 12:58:09 -07:00
event_delegate.go	Add network scoped gossip database	2016-04-08 12:58:09 -07:00
message.go	Add network scoped gossip database	2016-04-08 12:58:09 -07:00
networkdb.go	Fix gossip network event overwriting self	2016-04-25 09:47:36 -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