[
https://issues.apache.org/jira/browse/MESOS-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045985#comment-15045985
]
Joseph Wu edited comment on MESOS-4087 at 12/8/15 11:23 PM:
------------------------------------------------------------
Reviews:
|| Review || Summary||
| https://reviews.apache.org/r/41055/
https://reviews.apache.org/r/41057/ | Refactoring |
| https://reviews.apache.org/r/41002/ | Module interface |
| https://reviews.apache.org/r/41003/ | Default module implementation |
| https://reviews.apache.org/r/41004/ | Modularification |
| https://reviews.apache.org/r/41061/ | New agent flags |
| https://reviews.apache.org/r/41111/ | Regression test |
was (Author: kaysoky):
Reviews (WIP):
https://reviews.apache.org/r/41055/
https://reviews.apache.org/r/41057/
https://reviews.apache.org/r/41002/
https://reviews.apache.org/r/41003/
https://reviews.apache.org/r/41004/
> Introduce a module for logging executor/task output
> ---------------------------------------------------
>
> Key: MESOS-4087
> URL: https://issues.apache.org/jira/browse/MESOS-4087
> Project: Mesos
> Issue Type: Task
> Components: containerization, modules
> Reporter: Joseph Wu
> Assignee: Joseph Wu
> Labels: logging, mesosphere
>
> Existing executor/task logs are logged to files in their sandbox directory,
> with some nuances based on which containerizer is used (see background
> section in linked document).
> A logger for executor/task logs has the following requirements:
> * The logger is given a command to run and must handle the stdout/stderr of
> the command.
> * The handling of stdout/stderr must be resilient across agent failover.
> Logging should not stop if the agent fails.
> * Logs should be readable, presumably via the web UI, or via some other
> module-specific UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
