Ken Sipe commented on MESOS-6786:

[~gkleiman]  is there a plan to implement this?

> TASK_KILLED updates do not provide a reason why the task has been killed.
> -------------------------------------------------------------------------
>                 Key: MESOS-6786
>                 URL: https://issues.apache.org/jira/browse/MESOS-6786
>             Project: Mesos
>          Issue Type: Improvement
>    Affects Versions: 1.0.2, 1.1.0
>            Reporter: Gastón Kleiman
>            Priority: Major
>              Labels: executors, health-check
> 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

Reply via email to