[
https://issues.apache.org/jira/browse/MESOS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144634#comment-14144634
]
Alexander Rukletsov commented on MESOS-1143:
--------------------------------------------
Maybe we should agree on a general approach to adding new task states or
substates. There are several related issues, like [tasks that are implicitly
killed|https://issues.apache.org/jira/browse/MESOS-1736] as a reaction to
{{UnregisterFrameworkMessage}}, or [exposing additional
info|https://issues.apache.org/jira/browse/MESOS-343] through substates.
I would suggest we introduce new task states rather sparingly, but rather
create substates instead. I would opt for a single protobuf enum, something
like {{TaskStateExplained}}. There we can have fine-grained states, e.g.
whether the task failed because of an OOM event or whether it was killed
explicitly or implicitly.
> 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
>
> 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)
