[
https://issues.apache.org/jira/browse/MESOS-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247426#comment-14247426
]
David Robinson commented on MESOS-1375:
---------------------------------------
An alternative solution is to avoid the --log_dir option altogether and instead
pipe stdout/stderr through httpd's rotatelogs command. This allows you to
rotate logs as you please. logrotate's copytruncate option will cause extra
disk I/O and potentially lose some messages.
> 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)
