[
https://issues.apache.org/jira/browse/MESOS-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273184#comment-15273184
]
Michael Gummelt commented on MESOS-5197:
----------------------------------------
[~kaysoky] How can we solve this problem? I'm working with yet another
customer where this info would be invaluable. Generally "My command is
failing. What was the command?" Is a very common scenario.
> Log executor commands w/o verbose logs enabled
> ----------------------------------------------
>
> Key: MESOS-5197
> URL: https://issues.apache.org/jira/browse/MESOS-5197
> Project: Mesos
> Issue Type: Task
> Reporter: Michael Gummelt
> Assignee: Yong Tang
> Labels: mesosphere
>
> To debug executors, it's often necessary to know the command that ran the
> executor. For example, when Spark executors fail, I'd like to know the
> command used to invoke the executor (Spark uses the command executor in a
> docker container). Currently, it's only output if GLOG_v is enabled, but I
> don't think this should be a "verbose" output. It's a common debugging need.
> https://github.com/apache/mesos/blob/2e76199a3dd977152110fbb474928873f31f7213/src/docker/docker.cpp#L677
> cc [~kaysoky]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
