[jira] [Commented] (MESOS-1462) External Containerizer can leave a task indefinitely in STAGING if the `launch` fails

["Benjamin Mahler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020550#comment-14020550 ] 

Benjamin Mahler commented on MESOS-1462:
----------------------------------------

At the current time there are no enabled integration tests for the EC so I would prefer to keep the caveat that the EC is alpha software in 0.19.0. Can you assign to Till so he can follow up with this and the other necessary EC fixes in 0.19.1?

> External Containerizer can leave a task indefinitely in STAGING if the `launch` fails
> -------------------------------------------------------------------------------------
>
>                 Key: MESOS-1462
>                 URL: https://issues.apache.org/jira/browse/MESOS-1462
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.19.0
>            Reporter: Tom Arnfeld
>            Priority: Blocker
>
> Not sure where else to create issues regarding RC software, but I guess here is as good as anywhere to record it...
> I mentioned it to [~tillt] before so i'm not sure if he thought of a fix (or has one unpushed). Essentially when you launch a task through an external containerizer, if the {{launch}} command of the external process fails for whatever reason (e.g. the fetcher throws an error) the task will sit in the STAGING state and never be terminated.
> At this point, I think it's acceptable to think executor hasn't registered yet, though that's not guaranteed. I'm seeing this behaviour on 0.19.0-rc3.
> Ping [~bmahler] - I think this is worth holding up the vote to investigate.



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