Jana Radhakrishnan f649d5ae61 Do not hold ack channel in ack table after closing ... Once the bulksync ack channel is closed remove it from the ack table right away. There is no reason to keep it in the ack table and later delete it in the ack waiter. Ack waiter anyways has reference to the channel on which it is waiting. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>		2016-10-03 09:50:02 -07:00
..
broadcast.go	Recover from transient gossip failures	2016-09-19 15:58:14 -07:00
cluster.go	Do not hold ack channel in ack table after closing	2016-10-03 09:50:02 -07:00
delegate.go	Do not hold ack channel in ack table after closing	2016-10-03 09:50:02 -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
watch.go