Flavio Crisciani 2d2a2bc568 Fix reapTime logic in NetworkDB ...

- Added remainingReapTime field in the table event.
  Wihtout it a node that did not have a state for the element
  was marking the element for deletion setting the max reapTime.
  This was creating the possibility to keep the entry being resync
  between nodes forever avoding the purpose of the reap time
  itself.

- On broadcast of the table event the node owner was rewritten
  with the local node name, this was not correct because the owner
  should continue to remain the original one of the message

Signed-off-by: Flavio Crisciani <flavio.crisciani@docker.com>

2017-09-21 09:37:37 -07:00

libnetwork

Fix reapTime logic in NetworkDB

2017-09-21 09:37:37 -07:00

Description

No description provided

containersdockergogolang

512 MiB

Languages

Go 97.5%

Shell 1.2%

Dockerfile 0.6%

PowerShell 0.2%

Lua 0.2%

Other 0.1%