[
https://issues.apache.org/jira/browse/HADOOP-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205624#comment-13205624
]
Eric Charles commented on HADOOP-8055:
--------------------------------------
@harsh
Btw, how is the patch submission tested against 0.24 and 0.23. I don't see it
directly from:
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/585//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/585//console
Your previous post correctly summarized what I meant.
@tom
I don't think there's something fundamental, it's more about correct
comprehension of the returned messages and the behavior we can expect.
I just found strange that hdfs-site.xml and yarn.xml was in the folder, but not
core-site.xml (I was in fact wondering if something had changed in the
configuration rules).
If you start without core-site.xml (or with an empty core-site.xml) you've got
an exception with message "Exception in thread "main"
java.lang.IllegalArgumentException: Invalid URI for NameNode address (check
fs.defaultFS): file:/// has no authority."
It's quite confusing, the issue is in fact the absence of fs.default.name
property (and not fs.defaultFS as written in the message).
Also, if you invoke 'hadoop namenode -format' with that empty/absent
core-site.xml, hadoop does correctly the format in a self-decided tmp folder
12/02/10 18:22:19 INFO namenode.NNStorage: Storage directory
/tmp/hadoop-echarles/dfs/name has been successfully formatted.
(prolly the default /tmp/hadoop-${user.name}/dfs/name value)
After that format, it refuses anyway to start (why doesn't it reuse that format
file system?)
So, I would except a helpful error message for all commands in case of absence
of configuration.
It's just the 'more' things I can see here (user-friendliness).
Maybe there are good reasons for this, or maybe I misuse the system? Otherwise,
should I open a JIRA?
> 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
