You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2012/07/05 14:38:37 UTC
[jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407049#comment-13407049 ]
Hudson commented on HADOOP-8393:
--------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #304 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/304/])
svn merge -c 1338998 FIXES: HADOOP-8393 hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster. (phunt via tucu) (Revision 1356763)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1356763
Files :
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/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: 0.23.3
>
> 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