[
https://issues.apache.org/jira/browse/MESOS-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Budnik reassigned MESOS-6961:
------------------------------------
Assignee: Andrei Budnik
> Executors don't use glog for logging.
> -------------------------------------
>
> Key: MESOS-6961
> URL: https://issues.apache.org/jira/browse/MESOS-6961
> Project: Mesos
> Issue Type: Bug
> Components: executor
> Reporter: Alexander Rukletsov
> Assignee: Andrei Budnik
> Labels: log, mesosphere, newbie++
>
> Built-in Mesos executors use {{cout}}/{{cerr}} for logging. This is not only
> inconsistent with the rest of the codebase, it also complicates debugging,
> since, e.g., a stack trace is not printed on an abort. Having timestamps will
> be also a huge plus.
> Consider migrating logging in all built-in executors to glog.
> There have been reported issues related to glog internal state races when a
> process that has glog initialized {{fork-exec}}s another process that also
> initialize glog. We should investigate how this issue is related to this
> ticket, cc [~tillt], [~vinodkone], [~bmahler].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
