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/10/20 19:25:33 UTC
[jira] [Assigned] (MESOS-343) Expose TASK_FAILED reason to
Frameworks.
[ https://issues.apache.org/jira/browse/MESOS-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominic Hamon reassigned MESOS-343:
-----------------------------------
Assignee: Dominic Hamon
> 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)