[jira] [Comment Edited] (MESOS-343) Expose TASK_FAILED reason to Frameworks.

["Alexander Rukletsov (JIRA)" <ji...@apache.org>]

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

Alexander Rukletsov edited comment on MESOS-343 at 10/21/14 12:08 PM:
----------------------------------------------------------------------

We will need to sweep through the code and add actual reasons where {{TASK_FAILED}} is issued before closing the ticket, for example for {{EXECUTOR_OOM}} event.


was (Author: alex-mesos):
We will need to sweep through the code and add actual reasons where {{TASK_FAILED}} is issued before closing the ticket.

> Expose TASK_FAILED reason to Frameworks.
> ----------------------------------------
>
>                 Key: MESOS-343
>                 URL: https://issues.apache.org/jira/browse/MESOS-343
>             Project: Mesos
>          Issue Type: Story
>            Reporter: Benjamin Mahler
>            Assignee: Dominic Hamon
>            Priority: Minor
>
> We now have a message string inside TaskStatus that provides human readable information about TASK_FAILED.
> It would be good to add some structure to the failure reasons, for framework schedulers to act on programmatically.
> E.g.
> enum TaskFailure {
>   EXECUTOR_OOM;
>   EXECUTOR_OUT_OF_DISK;
>   EXECUTOR_TERMINATED;
>   SLAVE_LOST;
>   etc..
> }



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