You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Steven Schlansker (JIRA)" <ji...@apache.org> on 2015/05/08 01:30:02 UTC
[jira] [Comment Edited] (MESOS-1375) Log rotation capable
[ https://issues.apache.org/jira/browse/MESOS-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533595#comment-14533595 ]
Steven Schlansker edited comment on MESOS-1375 at 5/7/15 11:30 PM:
-------------------------------------------------------------------
A year later, and our disks are still filling up due to this issue. This is a really sad problem to have in 2015 :(
was (Author: stevenschlansker):
A year later, and our disks are still filling up due to this issue. This is a really sad problem to have in 2015 :(
Standard GLOG mechanics are probably not good enough until MESOS-2193 gets some attention.
> Log rotation capable
> --------------------
>
> Key: MESOS-1375
> URL: https://issues.apache.org/jira/browse/MESOS-1375
> Project: Mesos
> Issue Type: Improvement
> Components: master, slave
> Affects Versions: 0.18.0
> Reporter: Damien Hardy
> Labels: ops, twitter
>
> Please provide a way to let ops manage logs.
> A log4j like configuration would be hard but make rotation capable without restarting the service at least.
> Based on external logrotate tool would be great :
> * write to a constant log file name
> * check for file change (recreated by logrotate) before write
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)