[
https://issues.apache.org/jira/browse/MESOS-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244923#comment-14244923
]
Andy Zhang edited comment on MESOS-1375 at 12/12/14 10:56 PM:
--------------------------------------------------------------
We're currently implementing a hack similar to one described here:
https://www.mail-archive.com/[email protected]/msg00803.html
It would be nice to get this out of the box without having to modify the
wrapper (in case we bump versions & CLI changes). On second thought, maybe
would be better to keep this out of syslog, which can get pretty polluted?
was (Author: zhangbanger):
I'd vote for the latter (syslog redirect). We're currently implementing a hack
similar to one described here:
https://www.mail-archive.com/[email protected]/msg00803.html
It would be nice to get this out of the box without having to modify the
wrapper (in case we bump versions & CLI changes)
> 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)
