mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Browning (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MESOS-7861) Health and readiness check output inaccessible with default executor
Date Fri, 04 Aug 2017 18:44:00 GMT
Michael Browning created MESOS-7861:
---------------------------------------

             Summary: Health and readiness check output inaccessible with default executor
                 Key: MESOS-7861
                 URL: https://issues.apache.org/jira/browse/MESOS-7861
             Project: Mesos
          Issue Type: Bug
          Components: executor
            Reporter: Michael Browning
            Priority: Minor


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.



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

Mime
View raw message