[
https://issues.apache.org/jira/browse/MESOS-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-6063:
----------------------------
Description: Currently, when we restart Mesos Agent with different cgroups
subsystems, the exist containers would recover failed on newly added
subsystems. In this case, we ignore them and continue to perform {{usage}},
{{status}} and {{cleanup}} on them. It would be better that we track recovered
and prepared subsystems for a container. Then ignore perform {{update}},
{{wait}}, {{usage}}, {{status}} on them. (was: Currently, when we restart
Mesos Agent with different cgroups subsystems, the exist containers would
recover failed on newly added subsystems. In this case, we ignore them and
continue to perform `usage`, `status` and `cleanup` on them. It would be
better that we track recovered and prepared subsystems for a container. Then
ignore perform `update`, `wait`, `usage`, `status` on them.)
> Track recovered and prepared subsystems for a container
> -------------------------------------------------------
>
> Key: MESOS-6063
> URL: https://issues.apache.org/jira/browse/MESOS-6063
> Project: Mesos
> Issue Type: Improvement
> Components: cgroups
> Reporter: haosdent
> Assignee: haosdent
> Labels: cgroups
>
> Currently, when we restart Mesos Agent with different cgroups subsystems, the
> exist containers would recover failed on newly added subsystems. In this
> case, we ignore them and continue to perform {{usage}}, {{status}} and
> {{cleanup}} on them. It would be better that we track recovered and prepared
> subsystems for a container. Then ignore perform {{update}}, {{wait}},
> {{usage}}, {{status}} on them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
