[
https://issues.apache.org/jira/browse/MESOS-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628711#comment-15628711
]
Alexander Rukletsov commented on MESOS-4996:
--------------------------------------------
[~jieyu] is this still a bug? Shall we adjust the priority?
> 'containerizer->update' will always fail after killing a docker container.
> --------------------------------------------------------------------------
>
> Key: MESOS-4996
> URL: https://issues.apache.org/jira/browse/MESOS-4996
> Project: Mesos
> Issue Type: Bug
> Components: containerization, docker
> Affects Versions: 0.23.0, 0.23.1, 0.24.0, 0.24.1, 0.25.0, 0.26.0, 0.27.0,
> 0.27.1, 0.27.2, 0.28.0
> Reporter: Jie Yu
> Priority: Critical
> Labels: mesosphere
>
> Here is the sequence of events:
> 1) the framework does a killTask
> 2) killTask is handled by the docker executor
> 3) the docker executor calls docker->stop
> 4) docker container terminated
> 5) docker executor sends TASK_KILLED to the agent
> 6) since TASK_KILLED is terminal, agent calls containerizer->update()
> 7) DockerContainerizerProcess::update is called
> 8) Since pid is known, it tries to get the cgroups associated with the pid
> 9) Since pid has gone, cgroups::cpu::cgroup(pid) will return Error
> 10) We got "Failed to determine the cgroup hierarchy where the 'cpu'
> subsystem is mounted: Failed to read /proc/4390/cgroup: Failed to open file
> '/proc/4390/cgroup': No such file or directory"
> 11) containerizer->update fail, agent will call containerizer->destroy
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
