[ https://issues.apache.org/jira/browse/HDFS-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Srinivas updated HDFS-5316: ---------------------------------- Target Version/s: 2.2.0 > Namenode ignores the default https port > --------------------------------------- > > Key: HDFS-5316 > URL: https://issues.apache.org/jira/browse/HDFS-5316 > Project: Hadoop HDFS > Issue Type: Sub-task > Affects Versions: 2.0.0-alpha > Reporter: Suresh Srinivas > Priority: Critical > > 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: > {code} > 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")); > } > {code} > Unless https port is specifically configured as 0, we should not be picking > random port. This needs to be documented in hdfs-default.xml -- This message was sent by Atlassian JIRA (v6.1#6144)