[
https://issues.apache.org/jira/browse/MESOS-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152898#comment-16152898
]
Gastón Kleiman commented on MESOS-7861:
---------------------------------------
[~tillt] I think that the patches are safe and that {{git cherry-pick}} should
work without conflict, it'd be nice if it could be backported.
The only reason why they aren't in 1.4.x is because they landed on {{master}}
after the release candidates were cut.
> 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)
