[
https://issues.apache.org/jira/browse/MESOS-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336435#comment-15336435
]
Joseph Wu commented on MESOS-4087:
----------------------------------
Just to clarify, are you looking at the stdout/stderr of your {{spark-submit}}
command? Or are you looking at the [agent
sandboxes|http://mesos.apache.org/documentation/latest/sandbox/#where-is-it]
for your spark executors?
Under the default settings, the spark executors' sandboxes will have a
{{stdout}} and {{stderr}} file for their stdout/stderr logging. If {{log4j}}
places logs in a different location, you'll have to check that location.
> 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)
