You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Timothy Chen (JIRA)" <ji...@apache.org> on 2015/05/12 09:28:01 UTC

[jira] [Updated] (MESOS-2656) Slave should send status update immediately when container launch fails.

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

Timothy Chen updated MESOS-2656:
--------------------------------
    Fix Version/s: 0.23.0

> Slave should send status update immediately when container launch fails.
> ------------------------------------------------------------------------
>
>                 Key: MESOS-2656
>                 URL: https://issues.apache.org/jira/browse/MESOS-2656
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.22.1
>            Reporter: Jie Yu
>            Assignee: Jay Buffington
>             Fix For: 0.23.0
>
>
> Right now, the slave doesn't send status update to the scheduler if containerizer launch fails until executor reregistration timeout happens. Since for docker containerizer, someone might use a very large timeout value, ideally, the slave should send a status update to the scheduler right after containerizer launch fails.
> The simplest solution is to add a containerizer->destroy(..) in executorLaunched when containerizer->launch fails. In that way, it's going to trigger containerizer->wait and thus send status update to the scheduler.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)