[
https://issues.apache.org/jira/browse/MESOS-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gastón Kleiman updated MESOS-7861:
----------------------------------
Description:
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.
was:With the default executor, health and readiness checks are run in their
own nested containers, whose sandboxes are cleaned up after they terminate.
This makes access to stdout/stderr 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.
> Include check output in the DefaultExecutor log
> -----------------------------------------------
>
> Key: MESOS-7861
> URL: https://issues.apache.org/jira/browse/MESOS-7861
> Project: Mesos
> Issue Type: Bug
> Components: executor
> Affects Versions: 1.3.0
> Reporter: Michael Browning
> Priority: Minor
> Labels: check, default-executor, health-check, mesosphere
>
> 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)
