mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominic Hamon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-1930) Expose TASK_KILLED reason.
Date Mon, 03 Nov 2014 22:26:34 GMT

    [ https://issues.apache.org/jira/browse/MESOS-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195231#comment-14195231
] 

Dominic Hamon commented on MESOS-1930:
--------------------------------------

The current proposal in the review linked above adds a second tier of states as reasons. However,
this is a limited list and may not cover every eventuality.

How would you expect this artificial task status to be plumbed in through the executor?

> 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)

Mime
View raw message