see
https://github.com/eirslett/mesos/commit/7eac3da95fdd39a0fb96b8d8a883e72b6b9f9943
2015-11-06 15:34 GMT+01:00 Kamil Chmielewski :
> Try to cantact with https://github.com/eirslett
> He can have a PoC from MesosCon Europe hackathon with Mesos writting
> containers logs to Logstash.
>
> Cheers,
Try to cantact with https://github.com/eirslett
He can have a PoC from MesosCon Europe hackathon with Mesos writting
containers logs to Logstash.
Cheers,
Kamil
2015-11-06 15:26 GMT+01:00 Paul Bell :
> I've done a little reconnoitering, and the terrain looks to me as follows:
>
>1. Docker mai
I've done a little reconnoitering, and the terrain looks to me as follows:
1. Docker maintains container log files at
/var/lib/docker/containers//-json.log
2. Mesos maintains container STDOUT files at a
slave/framework/application specific location, e.g.,
/tmp/mesos/slaves/20151102
Hi Mauricio,
YeahI 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
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
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
I think maybe could try something like logstash/heka to collect containers
logs. Or use sentry as log library directly. So that could easily fetch and
analyze them in a web interface.
On Fri, Nov 6, 2015 at 10:40 AM, Mauricio Garavaglia <
mauriciogaravag...@gmail.com> wrote:
> Hi guys,
>
> How ca
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 co
8 matches
Mail list logo