hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3755) Log the command of launching containers
Date Tue, 02 Jun 2015 05:27:18 GMT

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

Jeff Zhang updated YARN-3755:
-----------------------------
    Description: 
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}

  was:
In the resource manager, 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 use 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 command 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}


> Log the command of launching containers
> ---------------------------------------
>
>                 Key: YARN-3755
>                 URL: https://issues.apache.org/jira/browse/YARN-3755
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            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)

Mime
View raw message