1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
moby--moby/libnetwork/networkdb
Jana Radhakrishnan 2bead02c87 Ignore delete events for non-existent entries
In networkdb we should ignore delete events for entries which doesn't
exist in the db. This is always true because if the entry did not exist
then the entry has been removed way earlier and got purged after the
reap timer and this notification is very stale.

Also there were duplicate delete notifications being sent to the
clients. One when the actual delete event was received from gossip and
later when the entry was getting reaped. The second notification is
unnecessary and may cause issues with the clients if they are not
coded for idempotency.

Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>
2016-08-18 13:57:24 -07:00
..
broadcast.go Make sure broadcast queue is valid broadcasting 2016-06-12 11:58:03 -07:00
cluster.go Ignore delete events for non-existent entries 2016-08-18 13:57:24 -07:00
delegate.go Ignore delete events for non-existent entries 2016-08-18 13:57:24 -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 Ignore delete events for non-existent entries 2016-08-18 13:57:24 -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