[HADOOP-5687] Hadoop NameNode throws NPE if fs.default.name is the default value

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.21.0
• Hadoop Flags: Reviewed
• Assignee: Philip Martin
• Reporter: Philip Martin
• Created: 16/Apr/09 00:43
• Updated: 26/Jan/15 22:47
• Resolved: 22/May/09 23:15

Description

Throwing NPE is confusing; instead, an exception with a useful string description could be thrown instead.

Issue Links

• duplicates: HDFS-42 NetUtils.createSocketAddr NPEs if dfs.datanode.ipc.address is not set for a data node
• is duplicated by: HADOOP-5200 NPE when the namenode comes up but the filesystem is set to file://
• is related to: HDFS-301 Provide better error messages when fs.default.name is invalid
• relates to: HADOOP-4573 NNThroughputBenchmark throws NPE if fs.default.name is not set
• relates to: HADOOP-2977 Null pointer exception when parsing config
• relates to: MAPREDUCE-406 setting fs.default.name to an invalid URI format kills init thread in JobTracker
• relates to: HADOOP-4313 ease-of-use: missing fs.default.name should be caught and give a helpful message
• relates to: HADOOP-5200 NPE when the namenode comes up but the filesystem is set to file://