You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexander Rukletsov (JIRA)" <ji...@apache.org> on 2017/10/16 18:38:01 UTC
[jira] [Updated] (MESOS-7305) Adjust the recover logic of
MesosContainerizer to allow standalone containers.
[ https://issues.apache.org/jira/browse/MESOS-7305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Rukletsov updated MESOS-7305:
---------------------------------------
Sprint: Mesosphere Sprint 57, Mesosphere Sprint 58, Mesosphere Sprint 59, Mesosphere Sprint 60, Mesosphere Sprint 61, Mesosphere Sprint 62, Mesosphere Sprint 63, Mesosphere Sprint 64, Mesosphere Sprint 65, Mesosphere Sprint 66 (was: Mesosphere Sprint 57, Mesosphere Sprint 58, Mesosphere Sprint 59, Mesosphere Sprint 60, Mesosphere Sprint 61, Mesosphere Sprint 62, Mesosphere Sprint 63, Mesosphere Sprint 64, Mesosphere Sprint 65)
> Adjust the recover logic of MesosContainerizer to allow standalone containers.
> ------------------------------------------------------------------------------
>
> Key: MESOS-7305
> URL: https://issues.apache.org/jira/browse/MESOS-7305
> Project: Mesos
> Issue Type: Task
> Components: containerization
> Reporter: Jie Yu
> Assignee: Joseph Wu
> Labels: mesosphere, storage
>
> The current recovery logic in MesosContainerizer assumes that all top level containers are tied to some Mesos executors. Adding standalone containers will invalid this assumption. The recovery logic must be changed to adapt to that.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)