You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gastón Kleiman (JIRA)" <ji...@apache.org> on 2016/12/13 15:53:58 UTC
[jira] [Created] (MESOS-6786) Include reason in TASK_KILLED updates
Gastón Kleiman created MESOS-6786:
-------------------------------------
Summary: Include reason in TASK_KILLED updates
Key: MESOS-6786
URL: https://issues.apache.org/jira/browse/MESOS-6786
Project: Mesos
Issue Type: Improvement
Reporter: Gastón Kleiman
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)