Jie Yu created MESOS-2657:
-----------------------------
Summary: Support multiple reasons in status update message.
Key: MESOS-2657
URL: https://issues.apache.org/jira/browse/MESOS-2657
Project: Mesos
Issue Type: Improvement
Reporter: Jie Yu
Sometimes, a single reason in the status update message makes it very hard for
frameworks to understand the cause of a status update. For example, we have
REASON_EXECUTOR_TERMINATED, but that's a very general reason and sometime we
want a sub-reason for that (e.g., REASON_CONTAINER_LAUNCH_FAILED) so that the
framework can better react to the status update.
We could change 'reason' field in TaskStatus to be a repeated field (should be
backward compatible). For instance, for a containerizer launch failure, we
probably need two reasons for TASK_LOST: 1) the top level reason
REASON_EXECUTOR_TERMINATED; 2) the second level reason
REASON_CONTAINER_LAUNCH_FAILED.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
