You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Marco Massenzio (JIRA)" <ji...@apache.org> on 2015/04/30 02:22:06 UTC
[jira] [Commented] (MESOS-1462) External Containerizer can leave a
task indefinitely in STAGING if the `launch` fails
[ https://issues.apache.org/jira/browse/MESOS-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520582#comment-14520582 ]
Marco Massenzio commented on MESOS-1462:
----------------------------------------
We are now on 0.22.x - is this still an issue?
Also, not sure why is this in the 'expedite' bucket?
> 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
> Assignee: Till Toenshoff
> 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.3.4#6332)