You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2014/08/25 23:24:58 UTC
[jira] [Assigned] (MESOS-1644) Provide a means to initialize GLOG
for the executor driver.
[ https://issues.apache.org/jira/browse/MESOS-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone reassigned MESOS-1644:
---------------------------------
Assignee: Vinod Kone
> Provide a means to initialize GLOG for the executor driver.
> -----------------------------------------------------------
>
> Key: MESOS-1644
> URL: https://issues.apache.org/jira/browse/MESOS-1644
> Project: Mesos
> Issue Type: Improvement
> Components: framework
> Reporter: Benjamin Mahler
> Assignee: Vinod Kone
>
> Currently we don't initialize google logging from the executor driver, but we do in the scheduler driver.
> Scheduler Driver: https://github.com/apache/mesos/blob/0.19.1/src/sched/sched.cpp#L1093
> Executor Driver (left as a TODO): https://github.com/apache/mesos/blob/0.19.1/src/exec/exec.cpp#L595
> This means that we don't have stacktraces available and it makes it hard to debug mysterious process exits.
--
This message was sent by Atlassian JIRA
(v6.2#6252)