[MESOS-1884] Composing Containerizer is not sending calls to still launching containers

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.21.0
• Component/s: containerization
• Target Version/s: 0.21.0
• Sprint: Mesosphere Q4 Sprint 1 10/31
• Assignee: Unassigned
• Reporter: Timothy Chen
• Created: 09/Oct/14 05:53
• Updated: 05/Nov/14 19:49
• Resolved: 05/Nov/14 19:49

Description

Currently the new composing containerizer it holds multiple containerizers and passes calls to the underlying containerizer that launched the container.

However, this introduces a new problem where the composing containerizer only forward update/destroy calls to the container once the container is finished launching, as it then internally updates the tracking structure which containerizer is a container launched with.

The symptom is that the containerizer that is launching a container won't get a destroy call and continue to launch the container, while the slave already removed the task and it became a orphaned container that is not tracked by Mesos.

Issue Links

• Is contained by: MESOS-1915 Docker containers that fail to launch are not killed