[
https://issues.apache.org/jira/browse/MESOS-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431967#comment-15431967
]
IvanJobs commented on MESOS-6056:
---------------------------------
Yep, I missed that part of log. log in sandbox is not only log from docker
container, but includes log from executor. docker daemon just maintain log from
docker container. If I redirect sandbox's log to /dev/null, I will lose log
from executor. Thx for reminding me of that.
As you say, we don't add features in Github PRs. But my understanding of that
ref link is not the same.
I picked two sentences out below:
"
You’ve fixed a bug or added a feature and want to contribute it. AWESOME!
Once your JIRA and Review Board accounts are in place please go ahead and
create a review or GitHub pull request with an entry for yourself in
contributors.yaml file.
"
did I miss something? thx.
> 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)
