Starting HDFS with blank configuration fails --------------------------------------------
Key: HDFS-2965 URL: https://issues.apache.org/jira/browse/HDFS-2965 Project: Hadoop HDFS Issue Type: Bug Components: name-node Affects Versions: 0.24.0 Reporter: Eric Charles Build a tar.gz distribution from hadoop trunk (on mac os x) Untar, blank *-site.xml configuration files are present in etc/conf 'bin/hadoop namenode -format' : succeds with ...12/02/17 11:53:32 INFO namenode.FSImage: Saving image file /tmp/hadoop-echarles/dfs/name/current/fsimage.ckpt_0000000000000000000 using no compression... 'sbin/start-dfs.sh' fails with Exception in thread "main" java.lang.IllegalArgumentException: Invalid URI for NameNode address (check fs.defaultFS): file:/// has no authority. Is this what we want (is this the expected behavior) ? If it formats with the blank configuration, I would rather expect that is also starts. The other way around is fail early on format with an message stating the missing configuration. If behavior can be defined here, I will try to produce a patch for it. Thx, Eric -- 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