Jana Radhakrishnan 5f5dad3c02 Recover from transient gossip failures ... Currently if there is any transient gossip failure in any node the recoevry process depends on other nodes propogating the information indirectly. In cases if these transient failures affects all the nodes that this node has in its memberlist then this node will be permenantly cutoff from the the gossip channel. Added node state management code in networkdb to address these problems by trying to rejoin the cluster via the failed nodes when there is a failure. This also necessitates the need to add new messages called node event messages to differentiate between node leave and node failure. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>		2016-09-19 15:58:14 -07:00
..
broadcast.go	Recover from transient gossip failures	2016-09-19 15:58:14 -07:00
cluster.go	Recover from transient gossip failures	2016-09-19 15:58:14 -07:00
delegate.go	Recover from transient gossip failures	2016-09-19 15:58:14 -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	Recover from transient gossip failures	2016-09-19 15:58:14 -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