[MESOS-1930] Expose TASK_KILLED reason.

• Type: Story
• Status: Accepted
• Priority: Minor
• Resolution: Unresolved
• Component/s: scheduler api
• Labels: api integration observability
• Epic Link: task-failure-reasons
• Sprint: Twitter Mesos Q4 Sprint 2, Twitter Mesos Q4 Sprint 3
• Assignee: Unassigned
• Reporter: Alex R
• Created: 15/Oct/14 17:37
• Updated: 29/Apr/19 09:27

Description

A task process may be killed by a SIGTERM or SIGKILL. The only possibility to check how the task process has exited is to examine the message: status.message().find("Terminated"). However, a task may not run in its own process, hence the executor may not be able to provide an exit status. What we actually want is an artificial task exit status that is rendered by the executor.

This may be resolved by adding second tier states or state explanations. Here is a link to a discussion: https://reviews.apache.org/r/26382/

Issue Links

• is related to: MESOS-343 Expose TASK_FAILED reason to Frameworks.
• is related to: MESOS-1830 Expose master stats differentiating between master-generated and slave-generated LOST tasks
• is related to: MESOS-1143 Add a TASK_ERROR task status.
• relates to: MESOS-6786 TASK_KILLED updates do not provide a reason why the task has been killed.