Hi Mauricio, Yeah....I see your point; thank you.
My approach would be akin to closing the barn door after the horse got out. Both Mesos & Docker are doing their own writing of STDOUT. Docker's rotation won't address Mesos's behavior. I need to find a solution here. -Paul On Thu, Nov 5, 2015 at 10:46 PM, Mauricio Garavaglia < mauriciogaravag...@gmail.com> wrote: > Hi Paul, > > I don't think that's going to help :( > Even if you configure a different docker log driver, Docker still send > things to stdout, which is catched by mesos and dumped in the .logs > directory in the job sandbox. For example, by default docker logs into a > json file in /var/lib/docker but mesos still writes to the sandbox. > Hi Mauricio, > > I'm grappling with the same issue. > > I'm not yet sure if it represents a viable solution, but I plan to look at > Docker's log rotation facility. It was introduced in Docker 1.8. > > If you beat me to it & it looks like a solution, please let us know! > > Thanks. > > Cordially, > > Paul > > > On Nov 5, 2015, at 9:40 PM, Mauricio Garavaglia < > mauriciogaravag...@gmail.com> wrote: > > > > Hi guys, > > > > How can I manage the stdout/err log files generated by jobs in mesos? > for long running docker apps launched using marathon the log files can > deplete the disk of an agent, and using quotas makes the jobs to be killed > which is also not ideal. I'd like to have a way to rotate them. > > > > Is it correct to just go to the mesos agent workdir and go through each > sandbox stdout/err and rotate them? I know that could break the log UI but > it doesn't scale very well having logs of several of GB. > > > > Thanks! >
