Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-7861

Include check output in the DefaultExecutor log

    XMLWordPrintableJSON

Details

    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.

      Attachments

        Activity

          People

            gkleiman Gastón Kleiman
            mrbrowning Michael Browning
            Greg Mann Greg Mann
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: