You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Qian Zhang (Jira)" <ji...@apache.org> on 2019/10/15 14:18:00 UTC
[jira] [Assigned] (MESOS-9964) Support destroying UCR containers in
provisioning state
[ https://issues.apache.org/jira/browse/MESOS-9964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Qian Zhang reassigned MESOS-9964:
---------------------------------
Assignee: Qian Zhang
> Support destroying UCR containers in provisioning state
> -------------------------------------------------------
>
> Key: MESOS-9964
> URL: https://issues.apache.org/jira/browse/MESOS-9964
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Reporter: Qian Zhang
> Assignee: Qian Zhang
> Priority: Major
> Labels: containerization
>
> Currently when destroying a UCR container, if the container is in provisioning state, we will wait for the provisioner to finish provisioning before we start destroying the container, see [here|https://github.com/apache/mesos/blob/1.9.0/src/slave/containerizer/mesos/containerizer.cpp#L2685:L2693] for details. This may cause the container stuck at destroying, and more seriously it may cause the subsequent containers created from the same image stuck at provisioning state, because if the first container was stuck at pulling the image somehow, the subsequent containers have to wait for the puller to finish the pulling, see [here|https://github.com/apache/mesos/blob/1.9.0/src/slave/containerizer/mesos/provisioner/docker/store.cpp#L341:L345] for details.
> So we'd better to support destroying the container in provisioning state so that the subsequent containers created from the same image will not be affected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)