[MESOS-6786] TASK_KILLED updates do not provide a reason why the task has been killed.

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.2, 1.1.0
• Component/s: scheduler api
• Labels: executors health-check integration observability
• Epic Link: task-failure-reasons
• Assignee: Unassigned
• Reporter: Gastón Kleiman
• Shepherd: Alex R
• Created: 13/Dec/16 15:53
• Updated: 29/Apr/19 09:26

Description

At least the following reasons can lead to a task being killed:

• The executor decided to kill it, e.g., if it was unhealthy.
• The framework requested the kill.
• An operator requested the kill.

The executors bundled with Mesos don't set a reason in the TaskStatus message, making it hard to debug task kills.

I think that we should extend the TaskStatus.Reason enum with reasons for those three cases.

In the case of health check failures, the executors should also populate the message field with useful debugging information.

Issue Links

• is related to: MESOS-1930 Expose TASK_KILLED reason.
• relates to: MESOS-6905 Task status updates caused by task health update do not set appropriate reason.