[
https://issues.apache.org/jira/browse/MESOS-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135973#comment-16135973
]
Greg Mann commented on MESOS-7861:
----------------------------------
{code}
commit 8347ec09f15989b822f48c000043c6547c25b5f4
Author: Gastón Kleiman <[email protected]>
Date: Mon Aug 21 15:28:39 2017 -0700
Raised the logging level of some check and health check messages.
Some users pointed out that always logging the result of checks and
health checks makes it easier to debug problems.
Review: https://reviews.apache.org/r/61791/
{code}
{code}
commit 6d778fa45a73723b857db9b2ce92c3d15fb3373f
Author: Gastón Kleiman <[email protected]>
Date: Mon Aug 21 15:28:37 2017 -0700
Made the log output handling of TCP and HTTP checks consistent.
Review: https://reviews.apache.org/r/61766/
{code}
{code}
commit 0a01bc38eba08da8ef8b4ae152c95a57c39d73f3
Author: Gastón Kleiman <[email protected]>
Date: Mon Aug 21 15:28:36 2017 -0700
Included nested command check output in the executor logs.
This patch updates the checker and health checker to include the output
of COMMAND checks and health checks in its logs by default. This has
the effect of including these logs in the executor output for easier
debugging.
Review: https://reviews.apache.org/r/61697/
{code}
> 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
>
> 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)
