You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Dominic Hamon (JIRA)" <ji...@apache.org> on 2014/11/04 23:21:34 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=14196959#comment-14196959 ] 

Dominic Hamon commented on MESOS-1143:
--------------------------------------

Added status as part of

commit ca13594054b179bd36ce14323de3111f92bae3cd (HEAD, origin/master, origin/HEAD, master, MESOS-1830.task_lost_source)
Author: Dominic Hamon <dh...@twitter.com>
Commit: Dominic Hamon <dh...@twitter.com>

    Add source and reason to TaskStatus.

    Review: https://reviews.apache.org/r/26382/

but not in use until 0.22.0

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