mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
89edb68e89
A node is no longer using its load balancer IP address when it no longer
has tasks that use the network that requires that load balancer. When
this occurs, the swarmkit manager will free that IP in IPAM, and may
reaassign it.
When a task shuts down cleanly, it attempts removal of the networks it
uses, and if it is the last task using those networks, this removal
succeeds, and the load balancer IP is freed.
However, this behavior is absent if the container fails. Removal of the
networks is never attempted.
To address this issue, I amend the executor. Whenever a node load
balancer IP is removed or changed, that information is passedd to the
executor by way of the Configure method. By keeping track of the set of
node NetworkAttachments from the previous call to Configure, we can
determine which, if any, have been removed or changed.
At first, this seems to create a race, by which a task can be attempting
to start and the network is removed right out from under it. However,
this is already addressed in the controller. The controller will attempt
to recreate missing networks before starting a task.
Signed-off-by: Drew Erny <derny@mirantis.com>
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| controllers/plugin | ||
| convert | ||
| executor | ||
| provider | ||
| cluster.go | ||
| configs.go | ||
| errors.go | ||
| filters.go | ||
| filters_test.go | ||
| helpers.go | ||
| listen_addr.go | ||
| listen_addr_linux.go | ||
| listen_addr_others.go | ||
| networks.go | ||
| noderunner.go | ||
| nodes.go | ||
| secrets.go | ||
| services.go | ||
| swarm.go | ||
| tasks.go | ||
| utils.go | ||