[HDFS-2965] Starting HDFS with blank configuration fails

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.0-alpha
• Component/s: namenode
• Assignee: Unassigned
• Reporter: Eric Charles
• Created: 17/Feb/12 11:00
• Updated: 06/May/16 05:31

Description

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

Issue Links

• is related to: HDFS-301 Provide better error messages when fs.default.name is invalid