Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 11 Apr 2011 16:00:05 +0000 (UTC)
From: "Tom White (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <289150444.49348.1302537605938.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-6953) start-{dfs,mapred}.sh scripts fail
 if HADOOP_HOME is not set
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tom White commented on HADOOP-6953:
-----------------------------------

Yes, please see the linked JIRAs HDFS-1823 and MAPREDUCE-2428 for the patches. There is no common part, so this JIRA can be closed when the linked JIRAs are.

> start-{dfs,mapred}.sh scripts fail if HADOOP_HOME is not set
> ------------------------------------------------------------
>
>                 Key: HADOOP-6953
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6953
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.21.0
>            Reporter: Tom White
>            Assignee: Tom White
>            Priority: Blocker
>             Fix For: 0.21.1, 0.22.0
>
>
> If the HADOOP_HOME environment variable is not set then the start and stop scripts for HDFS and MapReduce fail with "Hadoop common not found.". The start-all.sh and stop-all.sh scripts are not affected.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira