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

["Ian Downes (JIRA)" <ji...@apache.org>]

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

Ian Downes resolved MESOS-1538.
-------------------------------

    Resolution: Fixed

Branch: refs/heads/master
Commit: 74e09a82ed0f6a63b82864b0f7d8c8f5d4eace7f
Parents: d0046dc
Author: Ian Downes <id...@twitter.com>
Authored: Wed Jun 25 14:31:46 2014 -0700
Committer: Ian Downes <id...@twitter.com>
Committed: Wed Jun 25 14:59:01 2014 -0700

> 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
>
> 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)