[ https://issues.apache.org/jira/browse/YARN-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568606#comment-14568606 ]
Hadoop QA commented on YARN-3755: --------------------------------- \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 15m 43s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:red}-1{color} | tests included | 0m 0s | The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. | | {color:green}+1{color} | javac | 7m 35s | There were no new javac warning messages. | | {color:green}+1{color} | javadoc | 9m 41s | There were no new javadoc warning messages. | | {color:green}+1{color} | release audit | 0m 23s | The applied patch does not increase the total number of release audit warnings. | | {color:red}-1{color} | checkstyle | 0m 37s | The applied patch generated 3 new checkstyle issues (total was 58, now 60). | | {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that end in whitespace. | | {color:green}+1{color} | install | 1m 34s | mvn install still works. | | {color:green}+1{color} | eclipse:eclipse | 0m 33s | The patch built with eclipse:eclipse. | | {color:green}+1{color} | findbugs | 1m 13s | The patch does not introduce any new Findbugs (version 3.0.0) warnings. | | {color:green}+1{color} | yarn tests | 6m 9s | Tests passed in hadoop-yarn-server-nodemanager. | | | | 43m 32s | | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12736742/YARN-3755-1.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / 990078b | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/8160/artifact/patchprocess/diffcheckstylehadoop-yarn-server-nodemanager.txt | | hadoop-yarn-server-nodemanager test log | https://builds.apache.org/job/PreCommit-YARN-Build/8160/artifact/patchprocess/testrun_hadoop-yarn-server-nodemanager.txt | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/8160/testReport/ | | Java | 1.7.0_55 | | uname | Linux asf905.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | | Console output | https://builds.apache.org/job/PreCommit-YARN-Build/8160/console | This message was automatically generated. > Log the command of launching containers > --------------------------------------- > > Key: YARN-3755 > URL: https://issues.apache.org/jira/browse/YARN-3755 > Project: Hadoop YARN > Issue Type: Improvement > Affects Versions: 2.7.0 > Reporter: Jeff Zhang > Assignee: Jeff Zhang > Attachments: YARN-3755-1.patch > > > In the resource manager log, yarn would log the command for launching AM, > this is very useful. But there's no such log in the NN log for launching > containers. It would be difficult to diagnose when containers fails to launch > due to some issue in the commands. Although user can look at the commands in > the container launch script file, this is an internal things of yarn, usually > user don't know that. In user's perspective, they only know what commands > they specify when building yarn application. > {code} > 2015-06-01 16:06:42,245 INFO > org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher: Command > to launch container container_1433145984561_0001_01_000001 : > $JAVA_HOME/bin/java -server -Djava.net.preferIPv4Stack=true > -Dhadoop.metrics.log.level=WARN -Xmx1024m > -Dlog4j.configuratorClass=org.apache.tez.common.TezLog4jConfigurator > -Dlog4j.configuration=tez-container-log4j.properties > -Dyarn.app.container.log.dir=<LOG_DIR> -Dtez.root.logger=info,CLA > -Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster > 1><LOG_DIR>/stdout 2><LOG_DIR>/stderr > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)