[MESOS-8768] Provide custom reason for cascaded kill in a task group

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: scheduler api
• Labels: integration observability
• Epic Link: task-failure-reasons
• Assignee: Unassigned
• Reporter: Zhitao Li
• Created: 09/Apr/18 17:28
• Updated: 29/Apr/19 09:26

Description

Currently, if a task fails in a task group, other active tasks in the same group will see TASK_KILLED without any custom reason. We would like to provide a custom reason like REASON_TASK_GROUP_KILLED to distinguish whether the task is killed upon request of scheduler or upon a cascaded failure.

 

Open question: does any framework depends the value of this reason? If not, we probably can just change the reason without a opt-in mechanism from framework (i.e, a new framework capability).

Issue Links

• is related to: MESOS-8531 Some task status updates sent by the default executor don't contain a REASON.