[
https://issues.apache.org/jira/browse/MESOS-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336709#comment-15336709
]
Joseph Wu commented on MESOS-4087:
----------------------------------
Sounds like you're trying to build a custom solution for your specific
framework. You might want to ask in the Spark community on how they've done
logging.
The {{ContainerLogger}} (this JIRA) is meant to encompass the stdout/stderr of
*any* executor, and involves loading a module into your agents. If you are
willing to dip into C++, you can write your own appender/forwarder. Examples:
https://github.com/apache/mesos/tree/master/src/slave/container_loggers
> 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
> Fix For: 0.27.0
>
>
> 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)
