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

Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2015/01/07 22:57:35 UTC

[jira] [Commented] (MESOS-1143) Add a TASK_ERROR task status.

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

Adam B commented on MESOS-1143:
-------------------------------

commit 1c80d845431a57dd8c20e636ab7fc313602e4b49
Author: Connor Doyle <co...@mesosphere.io>
Date:   Wed Jan 7 13:33:16 2015 -0800

    TASK_ERROR is terminal
    
    TASK_ERROR was introduced as a new terminal state, but was not handled
    as such in mesos::internal::protobuf::isTerminalState.
    
    Review: https://reviews.apache.org/r/29610

> Add a TASK_ERROR task status.
> -----------------------------
>
>                 Key: MESOS-1143
>                 URL: https://issues.apache.org/jira/browse/MESOS-1143
>             Project: Mesos
>          Issue Type: Improvement
>          Components: framework, master
>            Reporter: Benjamin Hindman
>            Assignee: Dominic Hamon
>
> During task validation we drop tasks that have errors and send TASK_LOST status updates. In most circumstances a framework will want to relaunch a task that has gone lost, and in the event the task is actually malformed (thus invalid) this will result in an infinite loop of sending a task and having it go lost.



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