[
https://issues.apache.org/jira/browse/MESOS-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726491#comment-14726491
]
Benjamin Mahler commented on MESOS-3348:
----------------------------------------
{quote}
In some cases, the accumulation of these logs can completely fill up the
agent's disk and thereby kill the task or machine.
{quote}
With disk quota isolation, once the quota is exceeded the container will be
destroyed. I'm a little confused by this ticket, are you saying mesos should be
doing log rotation for stdout/stderr for the command executor? All executors?
You're not referring to the agent or master logs, yes? Would be great to
clarify the summary / description to be precise about which logs you're
referring to :)
> Add either log rotation or capped-size logging
> ----------------------------------------------
>
> Key: MESOS-3348
> URL: https://issues.apache.org/jira/browse/MESOS-3348
> Project: Mesos
> Issue Type: Story
> Affects Versions: 0.23.0
> Reporter: Joseph Wu
> Assignee: Joseph Wu
> Labels: mesosphere
>
> Tasks currently log their output (stdout/stderr) to files on an agent's disk.
> In some cases, the accumulation of these logs can completely fill up the
> agent's disk and thereby kill the task or machine.
> To prevent this, we should either implement a log rotation mechanism or
> capped-size logging.
> We will first scope out several possible approaches for log rotation/capping
> in a design document (see [MESOS-3356]). Once an approach is chosen, this
> story will be broken down into some corresponding issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
