hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4250) hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Date Wed, 16 May 2012 14:05:04 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276748#comment-13276748
] 

Hudson commented on MAPREDUCE-4250:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #1081 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1081/])
    MAPREDUCE-4250. hadoop-config.sh missing variable exports, causes Yarn jobs to fail with
ClassNotFoundException MRAppMaster. (phunt via tucu) (Revision 1339000)

     Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1339000
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/bin/yarn-config.sh

                
> hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException
MRAppMaster
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4250
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4250
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: nodemanager
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>             Fix For: 2.0.1
>
>         Attachments: MAPREDUCE-4250.patch
>
>
> This is the MR side of HADOOP-8393
> 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

        

Mime
View raw message