Jana Radhakrishnan 6034058dc3 Fix infinite loop in bulk sync ... Due to a slice management logic error the bulk sync for loop can go on indefinitely and eventually leading to an OOM error. Fixed the logic so that an infinite loop never occurs. Also changed the bulk sync wait timeout to use a timer rather than use time.After as time.After is known to consume a lot of memory when called in a tight loop. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>		2016-06-15 23:38:48 -07:00
..
broadcast.go	Make sure broadcast queue is valid broadcasting	2016-06-12 11:58:03 -07:00
cluster.go	Fix infinite loop in bulk sync	2016-06-15 23:38:48 -07:00
delegate.go	Make sure node map is valid before accessing it	2016-06-13 18:30:31 -07:00
event_delegate.go	Properly purge node networks when node goes away	2016-06-14 12:39:38 -07:00
message.go	Use protobuf in networkdb core messages	2016-05-17 09:18:24 -07:00
networkdb.go	Properly purge node networks when node goes away	2016-06-14 12:39:38 -07:00
networkdb.pb.go	Use protobuf in networkdb core messages	2016-05-17 09:18:24 -07:00
networkdb.proto	Use protobuf in networkdb core messages	2016-05-17 09:18:24 -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