You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Armand Grillet (JIRA)" <ji...@apache.org> on 2017/09/02 19:09:02 UTC
[jira] [Commented] (MESOS-7586) Make use of cout/cerr and glog
consistent.
[ https://issues.apache.org/jira/browse/MESOS-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151565#comment-16151565 ]
Armand Grillet commented on MESOS-7586:
---------------------------------------
https://reviews.apache.org/r/62018/
https://reviews.apache.org/r/62037/
> Make use of cout/cerr and glog consistent.
> ------------------------------------------
>
> Key: MESOS-7586
> URL: https://issues.apache.org/jira/browse/MESOS-7586
> Project: Mesos
> Issue Type: Bug
> Reporter: Andrei Budnik
> Assignee: Armand Grillet
> Priority: Minor
> Labels: debugging, log, newbie
>
> Some parts of mesos use glog before initialization of glog, hence messages via glog might not end up in a logdir:
> bq. WARNING: Logging before InitGoogleLogging() is written to STDERR
> The solution might be:
> {{cout/cerr}} should be used before logging initialization.
> {{glog}} should be used after logging initialization.
>
> Usually, main function has initialization pattern like:
> # load = flags.load(argc, argv) // Load flags from command line.
> # Check if flags are correct, otherwise print error message to cerr and then exit.
> # Check if user passed --help flag to print help message to cout and then exit.
> # Parsing and setup of environment variables. If this fails, EXIT macro is used to print error message via glog.
> # process::initialize()
> # logging::initialize()
>
> Steps 2 and 3 should use {{cout/cerr}} to eliminate any extra information generated by glog like current time, date and log level.
> It would be preferable to move step 6 between steps 3 and 4 safely, because {{logging::initialize()}} doesn’t depend on {{process::initialize()}}.
> In addition, initialization of glog should be added, where it's necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)