[ https://issues.apache.org/jira/browse/MESOS-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303752#comment-15303752 ]
Guangya Liu commented on MESOS-5197: ------------------------------------ I posted a patch here https://reviews.apache.org/r/37989/ for MESOS-5348. The solution is setting {{GLOG_v=1}} if agent start without GLOG_v configuration, this can make sure the docker-command-executor can always log message with {{GLOG_v=1}} to sandbox. > 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 > Fix For: 0.29.0 > > > 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)