[
https://issues.apache.org/jira/browse/MESOS-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-2115:
--------------------------
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 Q1 Sprint 10 - 5/30 (was: 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)
> Improve recovering Docker containers when slave is contained
> ------------------------------------------------------------
>
> Key: MESOS-2115
> URL: https://issues.apache.org/jira/browse/MESOS-2115
> Project: Mesos
> Issue Type: Epic
> Components: docker
> Reporter: Timothy Chen
> Assignee: Timothy Chen
> Labels: docker
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
