[
https://issues.apache.org/jira/browse/MESOS-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195985#comment-14195985
]
Alexander Rukletsov commented on MESOS-1930:
--------------------------------------------
"Reason" may be not a precise term for what I mean. If a task is killed, I
would like to get feedback how it terminated: gracefully or hard by a timeout.
In case of CommandExecutor this is supported via signal escalation. If an
executor doesn't distinguish between soft and hard kill, it can simply ignore
the second tier state. How about introducing something like
{{REASON_KILL_TIMEOUT}}?
> Expose TASK_KILLED reason.
> --------------------------
>
> Key: MESOS-1930
> URL: https://issues.apache.org/jira/browse/MESOS-1930
> Project: Mesos
> Issue Type: Story
> Reporter: Alexander Rukletsov
> Assignee: Dominic Hamon
> Priority: Minor
>
> 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/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
