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

Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2015/09/14 20:33:46 UTC

[jira] [Commented] (MESOS-2035) Add reason to containerizer proto Termination

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

Vinod Kone commented on MESOS-2035:
-----------------------------------

We are seeing this in production when we enabled disk isolation. Let's get this fixed asap. cc [~jieyu]

> 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: Joerg Schad
>              Labels: mesosphere
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)