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

Posted to issues@mesos.apache.org by "Till Toenshoff (JIRA)" <ji...@apache.org> on 2017/09/04 19:31:00 UTC

[jira] [Commented] (MESOS-7861) Include check output in the DefaultExecutor log

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

Till Toenshoff commented on MESOS-7861:
---------------------------------------

[~gkleiman] Should we backport this to 1.4.x?

> Include check output in the DefaultExecutor log
> -----------------------------------------------
>
>                 Key: MESOS-7861
>                 URL: https://issues.apache.org/jira/browse/MESOS-7861
>             Project: Mesos
>          Issue Type: Improvement
>          Components: executor
>    Affects Versions: 1.3.0
>            Reporter: Michael Browning
>            Assignee: Gastón Kleiman
>              Labels: check, default-executor, health-check, mesosphere
>             Fix For: 1.5.0
>
>
> With the default executor, health and readiness checks are run in their own nested containers, whose sandboxes are cleaned up right before performing the next check. This makes access to stdout/stderr of previous runs of the check command effectively impossible.
> Although the exit code of the command being run is reported in a task status, it is often necessary to see the command's actual output when debugging a framework issue, so the ability to access this output via the executor logs would be helpful.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)