[
https://issues.apache.org/jira/browse/MESOS-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595790#comment-15595790
]
Jie Yu commented on MESOS-6414:
-------------------------------
i don't quite get this "the task manipulates its own nested cgroup". How does
the task itself be able to manipulate its own cgroup? So it is running under
root?
If docker daemon does that, then this is a process interfere with croups
created by Mesos. Even if Mesos does not break, daemon might break as well.
> cgroups isolator cleanup failed when the hierarchy is cleanup by docker
> daemon
> -------------------------------------------------------------------------------
>
> Key: MESOS-6414
> URL: https://issues.apache.org/jira/browse/MESOS-6414
> Project: Mesos
> Issue Type: Bug
> Components: cgroups
> Reporter: Anindya Sinha
> Assignee: Anindya Sinha
> Priority: Minor
> Labels: containerizer
> Fix For: 1.2.0
>
>
> Now if we launch a docker container in Mesos containerizer, the racing may
> happen
> between docker daemon and Mesos containerizer during cgroups operations.
> For example, when the docker container which run in Mesos containerizer OOM
> exit,
> Mesos containerizer would destroy following hierarchies
> {code}
> /sys/fs/cgroup/freezer/mesos/<mesos-cgroup>/<docker-cgroup>
> /sys/fs/cgroup/freezer/mesos/<mesos-cgroup>
> {code}
> But the docker daemon may destroy
> {code}
> /sys/fs/cgroup/freezer/mesos/<mesos-cgroup>/<docker-cgroup>
> {code}
> at the same time.
> If the docker daemon destroy the hierarchy first, then the Mesos
> containerizer would
> failed during {{CgroupsIsolatorProcess::cleanup}} because it could not find
> that hierarchy
> when destroying.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
