You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Dominic Hamon (JIRA)" <ji...@apache.org> on 2014/11/03 23:30:35 UTC
[jira] [Assigned] (MESOS-2035) Add reason to containerizer proto
Termination
[ https://issues.apache.org/jira/browse/MESOS-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominic Hamon reassigned MESOS-2035:
------------------------------------
Assignee: Dominic Hamon
> Add reason to containerizer proto Termination
> ---------------------------------------------
>
> Key: MESOS-2035
> URL: https://issues.apache.org/jira/browse/MESOS-2035
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Affects Versions: 0.21.0
> Reporter: Dominic Hamon
> Assignee: Dominic Hamon
> Priority: Minor
>
> When an isolator kills a task, the reason is unknown. As part of MESOS-1830, the reason is set to a general one but ideally we would have the termination reason to pass through to the status update. We could also differentiate a bad command (using the Command executor) from a termination from an isolator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)