Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-5265

Namenode fails to start when dfs.https.port is unspecified

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      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)

        Attachments

        1. HDFS-5265.002.patch
          3 kB
          Haohui Mai
        2. HDFS-5265.001.patch
          2 kB
          Haohui Mai

          Activity

            People

            • Assignee:
              wheat9 Haohui Mai
              Reporter:
              wheat9 Haohui Mai
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: