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
Flavio Crisciani f585f33042 Node failure timeout fix
The time to keep a node failed into the failed node list
was originally supposed to be 24h.

If a node leaves explicitly it will be removed from the list of nodes
and put into the leftNodes list. This way the NotifyLeave event won't
insert it into the retry list.
NOTE: if the event is lost instead the behavior will be the same as a failed node.

If a node fails, the NotifyLeave will insert it into the failedNodes
list with a reapTime of 24h. This means that the node will be checked
for 24h before being completely forgot. The current check time is every
1 second and is done by the reconnectNode function.
The failed node list is updated every 2h instead.

Signed-off-by: Flavio Crisciani <flavio.crisciani@docker.com>
2017-05-22 17:19:31 -07:00
..
broadcast.go On send node envents, notify only if there are peers 2017-04-21 10:19:08 -07:00
cluster.go retry once on a bulk sync failure 2017-05-11 21:13:18 -07:00
delegate.go control-plane hardning: cleanup local state on peer leaving a network 2017-03-31 01:49:03 -07:00
event_delegate.go Node failure timeout fix 2017-05-22 17:19:31 -07:00
message.go Use protobuf in networkdb core messages 2016-05-17 09:18:24 -07:00
networkdb.go control-plane hardning: cleanup local state on peer leaving a network 2017-03-31 01:49:03 -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 Fix panic in networkdb test code 2017-03-15 23:26:32 -07:00
watch.go Generating node discovery events to the drivers from networkdb 2017-02-01 17:54:51 -08:00