[experimental] Simple container rescheduling on node failure#1578
[experimental] Simple container rescheduling on node failure#1578abronan merged 5 commits intodocker-archive:masterfrom
Conversation
cluster/config.go
Outdated
ea7afd3 to
b72d27f
Compare
cluster/watchdog.go
Outdated
There was a problem hiding this comment.
Any reason this trigger whole cluster reschedule, instead of just this engine? I think there could be a lot of events for a big cluster. Isn't just checking this container enough?
9352993 to
0220f36
Compare
|
@vieux we are working on the forced cleanup fix in moby/libnetwork#862. |
Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com>
Add rescheduling integration tests. Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com>
Signed-off-by: Victor Vieux <vieux@docker.com>
experimental/README.md~
Outdated
There was a problem hiding this comment.
@vieux This looks like it shouldn't be here it is a backup file
Signed-off-by: Victor Vieux <vieux@docker.com>
|
LGTM |
|
LGTM. |
|
LGTM |
[experimental] Simple container rescheduling on node failure
[experimental] Simple container rescheduling on node failure
See #1488 for details
When a node goes down, swarm will try to reschedule container on another machine.
Depends on moby/moby#19001 for IP stability.
Depends on #1569 for proper cleanup of old containers.