Return-Path: 
 <common-issues-return-26321-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 2F5949B2B
	for <apmail-hadoop-common-issues-archive@minotaur.apache.org>;
 Fri, 10 Feb 2012 16:49:24 +0000 (UTC)
Received: (qmail 21788 invoked by uid 500); 10 Feb 2012 16:49:23 -0000
Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org
Received: (qmail 21735 invoked by uid 500); 10 Feb 2012 16:49:23 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Reply-To: common-issues@hadoop.apache.org
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 21722 invoked by uid 99); 10 Feb 2012 16:49:23 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2012 16:49:23 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2012 16:49:20 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id CA9E41AF0F3
	for <common-issues@hadoop.apache.org>; Fri, 10 Feb 2012 16:48:59 +0000 (UTC)
Date: Fri, 10 Feb 2012 16:48:59 +0000 (UTC)
From: "Harsh J (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1448316134.24714.1328892539831.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2113505247.23864.1328875079428.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-8055) Distribution tar.gz does not
 contain etc/hadoop/core-site.xml
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Harsh J commented on HADOOP-8055:
---------------------------------

Tom - It would not resolve the issue if we just create the file, but I think what Eric meant to say was that he wanted to resolve it by adding fs.defaultFS and he could not find core-site.xml, and hence had to create it on his own.
                
> Distribution tar.gz does not contain etc/hadoop/core-site.xml
> -------------------------------------------------------------
>
>                 Key: HADOOP-8055
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8055
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.24.0
>            Reporter: Eric Charles
>            Assignee: Harsh J
>         Attachments: HADOOP-8055.patch, HADOOP-8055.patch
>
>
> A dist built from trunk (0.24.0-SNAPSHOT) does not contain a core-site.xml in $HADOOP_HOME/etc/hadoop/ folder.
> $HADOOP_HOME/sbin/start-dfs.sh without that folder gives an exception
> Exception in thread "main" java.lang.IllegalArgumentException: URI has an authority component
>  at java.io.File.<init>(File.java:368)
>  at org.apache.hadoop.hdfs.server.namenode.NNStorage.getStorageDirectory(NNStorage.java:310)
>  at org.apache.hadoop.hdfs.server.namenode.FSEditLog.init(FSEditLog.java:178)
> ...
> Manually creating $HADOOP_HOME/etc/hadoop/core-site.xml solves this problem and hadoop starts fine.

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