[jira] [Commented] (MESOS-4086) Containerizer logging modularization

["James DeFelice (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054825#comment-15054825 ] 

James DeFelice commented on MESOS-4086:
---------------------------------------

I left this comment in the design doc too, related to the logging module API call that's invoked per-executor creation:
{quote}
I'd like to see the executor labels passed in here so that frameworks can advertise additional metadata for logging modules to take advantage of. for example, one or more LOGDIRSx=... vars could instruct the logging module to monitor additional directories in the sandbox for log files.
{quote}

> Containerizer logging modularization
> ------------------------------------
>
>                 Key: MESOS-4086
>                 URL: https://issues.apache.org/jira/browse/MESOS-4086
>             Project: Mesos
>          Issue Type: Epic
>          Components: containerization, modules
>            Reporter: Joseph Wu
>            Assignee: Joseph Wu
>              Labels: logging, mesosphere
>
> Executors and tasks are configured (via the various containerizers) to write their output (stdout/stderr) to files ("stdout" and "stderr") on an agent's disk.
> Unlike Master/Agent logs, executor/task logs are not attached to any formal logging system, like {{glog}}.  As such, there is significant scope for improvement.
> By introducing a module for logging, we can provide a common/programmatic way to access and manage executor/task logs.  Modules could implement additional sinks for logs, such as:
> * to the sandbox (the status quo),
> * to syslog,
> * to journald
> This would also provide the hooks to deal with logging related problems, such as:
> * the (current) lack of log rotation,
> * searching through executor/task logs (i.e. via aggregation)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)