Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 29 Nov 2011 22:35:40 +0000 (UTC)
From: "Mahadev konar (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1037286430.23600.1322606140457.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <112795080.4474.1322004759895.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3456) $HADOOP_PREFIX/bin/yarn should
 set defaults for $HADOOP_*_HOME
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mahadev konar updated MAPREDUCE-3456:
-------------------------------------

    Priority: Blocker  (was: Critical)
    
> $HADOOP_PREFIX/bin/yarn should set defaults for $HADOOP_*_HOME
> --------------------------------------------------------------
>
>                 Key: MAPREDUCE-3456
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3456
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Eric Payne
>            Priority: Blocker
>
> If the $HADOOP_PREFIX/hadoop-dist/target/hadoop-0.23.0-SNAPSHOT.tar.gz tarball is used to distribute hadoop, all of the HADOOP components (HDFS, MAPRED, COMMON) are all under one directory. In this use case, HADOOP_PREFIX should be set and should point to the root directory for all components, and it should not be necessary to set HADOOP_HDFS_HOME, HADOOP_COMMON_HOME, and HADOOP_MAPRED_HOME. However, the $HADOOP_PREFIX/bin/yarn script requires these 3 to be set explicitly in the calling environment or it won't run.
> $HADOOP_PREFIX/bin/yarn should check if $HADOOP_PREFIX is set and, if it is, use that value for the 3 other HADOOP_*_HOME variables.

--
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