You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Joseph Wu (JIRA)" <ji...@apache.org> on 2015/12/10 01:48:10 UTC
[jira] [Commented] (MESOS-4088) Modularize existing plain-file
logging for executor/task logs
[ https://issues.apache.org/jira/browse/MESOS-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049749#comment-15049749 ]
Joseph Wu commented on MESOS-4088:
----------------------------------
|| Reviews || Summary ||
| https://reviews.apache.org/r/41166/ | Add {{ExecutorLogger}} to {{Containerizer::Create}} |
| https://reviews.apache.org/r/41167/ | Initialize and call the {{ExecutorLogger}} in {{MesosContainerizer::_launch}} |
| https://reviews.apache.org/r/41168/ | Update {{MesosTest}} |
| https://reviews.apache.org/r/41169/ | Update {{MesosContainerizer}} tests |
> Modularize existing plain-file logging for executor/task logs
> -------------------------------------------------------------
>
> Key: MESOS-4088
> URL: https://issues.apache.org/jira/browse/MESOS-4088
> Project: Mesos
> Issue Type: Task
> Components: modules
> Reporter: Joseph Wu
> Assignee: Joseph Wu
> Labels: logging, mesosphere
>
> Once a module for executor/task output logging has been introduced, the default module will mirror the existing behavior. Executor/task stdout/stderr is piped into files within the executor's sandbox directory.
> The files are exposed in the web UI, via the {{/files}} endpoint.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)