You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2014/07/14 23:02:07 UTC

[jira] [Updated] (MESOS-1538) A container destruction in the middle of a launch leads to CHECK failure.

     [ https://issues.apache.org/jira/browse/MESOS-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Mahler updated MESOS-1538:
-----------------------------------

    Summary: A container destruction in the middle of a launch leads to CHECK failure.  (was: A container destruction in the middle of a launch leads to CHECK failure)

> A container destruction in the middle of a launch leads to CHECK failure.
> -------------------------------------------------------------------------
>
>                 Key: MESOS-1538
>                 URL: https://issues.apache.org/jira/browse/MESOS-1538
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>            Assignee: Ian Downes
>             Fix For: 0.19.1
>
>
> There is a race between the destroy() and exec() in the containerizer process, when the destroy is called in the middle of the launch.
> In particular if the destroy is completed and the container removed from 'promises' map before 'exec()' was called, CHECK failure happens.
> The fix is to return a Failure instead of doing a CHECK in 'exec()'.



--
This message was sent by Atlassian JIRA
(v6.2#6252)