[HDFS-5265] Namenode fails to start when dfs.https.port is unspecified

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.0
• Hadoop Flags: Reviewed
• Assignee: Haohui Mai
• Reporter: Haohui Mai
• Created: 26/Sep/13 17:39
• Updated: 30/Jun/15 07:25
• Resolved: 27/Sep/13 22:08

Description

Namenode get the wrong address when dfs.https.port is unspecified.

java.lang.IllegalArgumentException: Does not contain a valid host:port authority: 0.0.0.0:0.0.0.0:0
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:212)
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:163)
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:152)
at org.apache.hadoop.hdfs.server.namenode.NameNodeHttpServer.start(NameNodeHttpServer.java:102)
at org.apache.hadoop.hdfs.server.namenode.NameNode.startHttpServer(NameNode.java:633)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:490)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:691)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:676)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1265)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1331)