You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Hindman (JIRA)" <ji...@apache.org> on 2015/12/21 18:58:47 UTC

[jira] [Updated] (MESOS-4136) Add a ContainerLogger module that restrains log sizes

     [ https://issues.apache.org/jira/browse/MESOS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Hindman updated MESOS-4136:
------------------------------------
    Sprint: Mesosphere Sprint 24, Mesosphere Sprint 25  (was: Mesosphere Sprint 24)

> Add a ContainerLogger module that restrains log sizes
> -----------------------------------------------------
>
>                 Key: MESOS-4136
>                 URL: https://issues.apache.org/jira/browse/MESOS-4136
>             Project: Mesos
>          Issue Type: Improvement
>          Components: modules
>            Reporter: Joseph Wu
>            Assignee: Joseph Wu
>              Labels: logging, mesosphere
>
> One of the major problems this logger module aims to solve is overflowing executor/task log files.  Log files are simply written to disk, and are not managed other than via occasional garbage collection by the agent process (and this only deals with terminated executors).
> We should add a {{ContainerLogger}} module that truncates logs as it reaches a configurable maximum size.  Additionally, we should determine if the web UI's {{pailer}} needs to be changed to deal with logs that are not append-only.
> This will be a non-default module which will also serve as an example for how to implement the module.



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