[jira] [Updated] (YARN-3755) Log the command of launching containers
[
https://issues.apache.org/jira/browse/YARN-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated YARN-3755:
--
Labels: oct16-easy (was: )
> Log the command of launching containers
> ---
>
> Key: YARN-3755
> URL: https://issues.apache.org/jira/browse/YARN-3755
> Project: Hadoop YARN
> Issue Type: Sub-task
>Affects Versions: 2.7.0
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Labels: oct16-easy
> Attachments: YARN-3755-1.patch, YARN-3755-2.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_01 :
> $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= -Dtez.root.logger=info,CLA
> -Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster
> 1>/stdout 2>/stderr
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3755) Log the command of launching containers
[
https://issues.apache.org/jira/browse/YARN-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-3755:
--
Target Version/s: 2.7.4 (was: 2.7.3)
2.7.3 is under release process, changing target-version to 2.7.4.
> Log the command of launching containers
> ---
>
> Key: YARN-3755
> URL: https://issues.apache.org/jira/browse/YARN-3755
> Project: Hadoop YARN
> Issue Type: Sub-task
>Affects Versions: 2.7.0
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Attachments: YARN-3755-1.patch, YARN-3755-2.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_01 :
> $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= -Dtez.root.logger=info,CLA
> -Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster
> 1>/stdout 2>/stderr
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3755) Log the command of launching containers
[
https://issues.apache.org/jira/browse/YARN-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-3755:
--
Target Version/s: 2.7.3 (was: 2.7.2)
Moving out all non-critical / non-blocker issues that didn't make it out of
2.7.2 into 2.7.3.
> Log the command of launching containers
> ---
>
> Key: YARN-3755
> URL: https://issues.apache.org/jira/browse/YARN-3755
> Project: Hadoop YARN
> Issue Type: Sub-task
>Affects Versions: 2.7.0
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Attachments: YARN-3755-1.patch, YARN-3755-2.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_01 :
> $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= -Dtez.root.logger=info,CLA
> -Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster
> 1>/stdout 2>/stderr
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3755) Log the command of launching containers
[
https://issues.apache.org/jira/browse/YARN-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated YARN-3755:
-
Issue Type: Sub-task (was: Improvement)
Parent: YARN-522
> Log the command of launching containers
> ---
>
> Key: YARN-3755
> URL: https://issues.apache.org/jira/browse/YARN-3755
> Project: Hadoop YARN
> Issue Type: Sub-task
>Affects Versions: 2.7.0
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Attachments: YARN-3755-1.patch, YARN-3755-2.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_01 :
> $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= -Dtez.root.logger=info,CLA
> -Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster
> 1>/stdout 2>/stderr
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3755) Log the command of launching containers
[
https://issues.apache.org/jira/browse/YARN-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Zhang updated YARN-3755:
-
Attachment: YARN-3755-2.patch
Upload new patch to address the checkstyle issue
> 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, YARN-3755-2.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_01 :
> $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= -Dtez.root.logger=info,CLA
> -Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster
> 1>/stdout 2>/stderr
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3755) Log the command of launching containers
[
https://issues.apache.org/jira/browse/YARN-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Zhang updated YARN-3755:
-
Target Version/s: 2.7.1
> 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_01 :
> $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= -Dtez.root.logger=info,CLA
> -Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster
> 1>/stdout 2>/stderr
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3755) Log the command of launching containers
[
https://issues.apache.org/jira/browse/YARN-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Zhang updated YARN-3755:
-
Attachment: YARN-3755-1.patch
> 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_01 :
> $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= -Dtez.root.logger=info,CLA
> -Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster
> 1>/stdout 2>/stderr
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3755) Log the command of launching containers
[
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_01 : $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= -Dtez.root.logger=info,CLA
-Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster 1>/stdout
2>/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_01 : $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= -Dtez.root.logger=info,CLA
-Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster 1>/stdout
2>/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_01 :
> $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= -Dtez.root.logger=info,CLA
> -Dsun.nio.ch.bugLevel='' org.apache.tez.dag.app.DAGAppMaster
> 1>/stdout 2>/stderr
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
