mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rukletsov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-6961) Executors don't use glog for logging.
Date Wed, 07 Jun 2017 14:02:18 GMT

     [ https://issues.apache.org/jira/browse/MESOS-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Rukletsov updated MESOS-6961:
---------------------------------------
        Shepherd: Alexander Rukletsov
          Sprint: Mesosphere Sprint 57
    Story Points: 1

> 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)

Mime
View raw message