[MESOS-2115] Improve recovering Docker containers when slave is contained

• Type: Epic
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.23.0
• Component/s: docker
• Labels: docker
• Epic Name: Recover docker in slave container
• Target Version/s: 0.23.0
• Sprint: Mesosphere Q4 Sprint 3 - 12/7, Mesosphere Q1 Sprint 1 - 1/23, Mesosphere Q1 Sprint 2 - 2/6, Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1 Sprint 9 - 5/15, Mesosphere Sprint 10
• Assignee: Timothy Chen
• Reporter: Timothy Chen
• Shepherd: Benjamin Hindman
• Created: 14/Nov/14 18:52
• Updated: 03/Nov/16 20:08
• Resolved: 25/May/15 17:43

Description

Currently when docker containerizer is recovering it checks the checkpointed executor pids to recover which containers are still running, and remove the rest of the containers from docker ps that isn't recognized.

This is problematic when the slave itself was in a docker container, as when the slave container dies all the forked processes are removed as well, so the checkpointed executor pids are no longer valid.

We have to assume the docker containers might be still running even though the checkpointed executor pids are not.

Issue Links

• Blocked: MESOS-6536 Failed to recovery Docker containers when slave is containerized
• blocks: MESOS-2727 0.23.0 Release