[
https://issues.apache.org/jira/browse/MESOS-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432112#comment-15432112
]
ASF GitHub Bot commented on MESOS-6056:
---------------------------------------
Github user IvanJobs commented on the issue:
https://github.com/apache/mesos/pull/159
Well, actually after communication with Joseph Wu, I think this NOOP
Container Logger is not so common and should not be accept by mesos community.
So just forget about it. But if you have special use case and want to use this,
I'm happy about that
> add NOOP Container Logger for mesos
> -----------------------------------
>
> Key: MESOS-6056
> URL: https://issues.apache.org/jira/browse/MESOS-6056
> Project: Mesos
> Issue Type: Improvement
> Components: containerization, slave
> Affects Versions: 1.0.0
> Environment: mesos 1.0.0, docker
> Reporter: IvanJobs
> Priority: Trivial
> Labels: easyfix, features
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> mesos has two Container Loggers in its source files.
> One is build into mesos-agent: sandbox Container Logger, it just redirects
> stderr/stdout to sandbox, causing fill disk usage problem.
> The other is LogrotateContainerLogger module lib, it's good, we can make sure
> stdout/stderr in sandbox be in a constant size.
> But there is a common need: don't write stdout/stderr into sandbox, pity, we
> don't have any flags for turning it off.
> This is a come around for this: developing a new module lib for
> ContainerLogger for doing nothing(redirect stdout/stderr to /dev/null)
> yep, that's it. We need a NOOP ContainerLogger, BTW, FYI, we can also
> retrieve stderr/stdout from docker daemon either.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
