You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:28:11 UTC

[jira] [Issue Comment Deleted] (MESOS-1930) Expose TASK_KILLED reason.

     [ https://issues.apache.org/jira/browse/MESOS-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated MESOS-1930:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> Expose TASK_KILLED reason.
> --------------------------
>
>                 Key: MESOS-1930
>                 URL: https://issues.apache.org/jira/browse/MESOS-1930
>             Project: Mesos
>          Issue Type: Story
>          Components: scheduler api
>            Reporter: Alexander Rukletsov
>            Priority: Minor
>              Labels: api, integration, observability
>
> 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
(v7.6.3#76005)