mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kone <vi...@twitter.com>
Subject Re: Mesos logging configuration questions
Date Thu, 23 Jan 2014 06:59:29 GMT
I'm not able to repro this behavior. What version of Mesos are you running?

➜  build git:(vinod/slave_bootid_fix) ./bin/mesos-master.sh
I0122 22:57:56.434144 2096390528 main.cpp:126] Build: 2014-01-14 16:52:48
by vinod
I0122 22:57:56.435078 2096390528 main.cpp:167] Starting Mesos master
I0122 22:57:56.435622 46166016 master.cpp:284] Master started on
192.168.1.117:5050
I0122 22:57:56.435703 46166016 master.cpp:298] Master ID:
201401222257-1963043008-5050-47848
I0122 22:57:56.435717 46166016 master.cpp:308] Master allowing
unauthenticated frameworks to register!!
I0122 22:57:56.441432 46166016 master.cpp:732] The newly elected leader is
master@192.168.1.117:5050
I0122 22:57:56.441460 46166016 master.cpp:740] Elected as the leading
master!

➜  build git:(vinod/slave_bootid_fix) ls /tmp | grep master
➜  build git:(vinod/slave_bootid_fix)



@vinodkone


On Tue, Jan 21, 2014 at 4:19 PM, Jim Freeman <jimfr@sbcglobal.net> wrote:

> I'm not specifying --log_dir for master and slave startup, yet master and
> slave logs are being written to /tmp.  For example
> /tmp/mesos-master.jifreem-VirtualBox.jifreem.log.INFO.20140121-152544.3064
>
>   ------------------------------
>  *From:* Vinod Kone <vinod@twitter.com>
> *To:* "user@mesos.apache.org" <user@mesos.apache.org>
> *Sent:* Tuesday, January 21, 2014 11:06 AM
>
> *Subject:* Re: Mesos logging configuration questions
>
> If --log_dir is not specified nothing is written to disk.
>
> ➜  build git:(master) ✗ ./bin/mesos-master.sh --help
> ...
> ...
>   --log_dir=VALUE        Location to put log files (no default, nothing
>                                   is written to disk unless specified;
>                                   does not affect logging to stderr)
> ...
> ...
>
>
> @vinodkone
>
>
> On Tue, Jan 21, 2014 at 10:59 AM, Jim Freeman <jim.freeman@oracle.com>wrote:
>
> So if you don't supply --log_dir, then logs go in the /tmp executor
> sandbox?
>
> *From:* Benjamin Mahler [mailto:benjamin.mahler@gmail.com]
> *Sent:* Tuesday, January 21, 2014 10:45 AM
> *To:* user@mesos.apache.org; Jim Freeman
> *Subject:* Re: Mesos logging configuration questions
>
> I'm afraid that document is out of date, please ignore the comments
> related to MESOS_HOME in the interim of us fixing that document.
> https://issues.apache.org/jira/browse/MESOS-934
>
>  --log_dir is a parameter of the mesos-master and mesos-slave binaries.
>
> The directory you linked is to an executor sandbox, the note about
> MESOS_HOME/work is no longer correct.
>
> On Tue, Jan 14, 2014 at 2:48 PM, Jim Freeman <jimfr@sbcglobal.net> wrote:
> Referring to
> http://mesos.apache.org/documentation/latest/logging-and-debugging/  :
>
> I have not set MESOS_HOME, so it should default per the doc.
>
> 1) Doc says "Mesos uses the Google Logging library and writes logs to
> MESOS_HOME/logs by default, where MESOS_HOME is the location where Mesos is
> installed."
>
> How do I determine where Mesos is installed?  The 'make' put Mesos files
> in various places.
>
> I do see mesos-log.* files directly in /tmp (not in a */logs directory)
>
> 2) Doc says "The log directory can be *configured *using the log_dir
> parameter."
>
> log_dir parameter to what?  'configured' is a web link that might tell me,
> but it links to a nonexistent web page.
>
> 3) Doc says "Frameworks that run on Mesos have their output stored to a
> "work" directory on each machine. By default, this is MESOS_HOME/work."
>
> Yet I only find stderr and stdout text files in paths like this (note
> there is no "work" component"):
>
>
> /tmp/mesos/slaves/201401131343-16842879-5050-5210-0/frameworks/201401131343-16842879-5050-5210-0000/executors/default/runs/43bf587e-63df-4f26-b698-ab5c9e8ed385
>
>
>
>
>
>

Mime
View raw message