[HDFS-5316] Namenode ignores the default https port

• Type: Sub-task
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.0-alpha
• Fix Version/s: 2.3.0
• Target Version/s: 2.2.0
• Assignee: Haohui Mai
• Reporter: Suresh Srinivas
• Created: 07/Oct/13 18:31
• Updated: 24/Feb/14 20:57
• Resolved: 08/Oct/13 04:58

Description

When dfs.https.enable is true and dfs.https.port is not configured, namenode does not pickup the default https port (50470), instead picks up random port. See:

boolean needClientAuth = conf.getBoolean("dfs.https.need.client.auth", false);
      InetSocketAddress secInfoSocAddr = NetUtils.createSocketAddr(infoHost + ":" + conf.get(
        DFSConfigKeys.DFS_NAMENODE_HTTPS_PORT_KEY, "0"));
      Configuration sslConf = new Configuration(false);
      if (certSSL) {
        sslConf.addResource(conf.get(DFSConfigKeys.DFS_SERVER_HTTPS_KEYSTORE_RESOURCE_KEY,
                                     "ssl-server.xml"));
      }

Unless https port is specifically configured as 0, we should not be picking random port. This needs to be documented in hdfs-default.xml