[
https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276754#comment-13276754
]
Hudson commented on HADOOP-8393:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk #1081 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1081/])
HADOOP-8393. hadoop-config.sh missing variable exports, causes Yarn jobs to
fail with ClassNotFoundException MRAppMaster. (phunt via tucu) (Revision
1338998)
Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1338998
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
> hadoop-config.sh missing variable exports, causes Yarn jobs to fail with
> ClassNotFoundException MRAppMaster
> -----------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8393
> URL: https://issues.apache.org/jira/browse/HADOOP-8393
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 2.0.1
>
> Attachments: HADOOP-8393.patch
>
>
> If you start a pseudo distributed yarn using "start-yarn.sh" you need to
> specify exports for HADOOP_COMMON_HOME, HADOOP_HDFS_HOME, YARN_HOME,
> YARN_CONF_DIR, and HADOOP_MAPRED_HOME in hadoop-env.sh (or elsewhere),
> otherwise the spawned node manager will be missing these in it's environment.
> This is due to start-yarn using yarn-daemons. With this fix it's possible to
> start yarn (etc...) with only HADOOP_CONF_DIR specified in the environment.
> Took some time to track down this failure, so seems worthwhile to fix.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
