You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2016/03/19 00:21:33 UTC
[jira] [Created] (MESOS-4985) Destroy a container while it's
provisioning can lead to leaked provisioned directories.
Jie Yu created MESOS-4985:
-----------------------------
Summary: Destroy a container while it's provisioning can lead to leaked provisioned directories.
Key: MESOS-4985
URL: https://issues.apache.org/jira/browse/MESOS-4985
Project: Mesos
Issue Type: Bug
Affects Versions: 0.28.0
Reporter: Jie Yu
Priority: Critical
Fix For: 0.28.1
Here is the possible sequence of events:
1) containerizer->launch
2) provisioner->provision is called. it is fetching the image
3) executor registration timed out
4) containerizer->destroy is called
5) container->state is still in PREPARING
6) provisioner->destroy is called
So we can be calling provisioner->destory while provisioner->provision hasn't finished yet. provisioner->destroy might just skip since there's no information about the container yet, and later, provisioner will prepare the root filesystem. This root filesystem will not be destroyed as destroy already finishes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)