Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Date: Wed, 16 May 2012 04:22:15 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: 
 <2139004669.2458.1337142135753.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2042486601.55649.1336762490482.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (MAPREDUCE-4250) hadoop-config.sh missing
 variable exports, causes Yarn jobs to fail with ClassNotFoundException
 MRAppMaster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alejandro Abdelnur resolved MAPREDUCE-4250.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.1
     Hadoop Flags: Reviewed

Thanks Patrick. committed to trunk and branch-2.
                
> 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