[
https://issues.apache.org/jira/browse/HDFS-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788908#comment-13788908
]
Brandon Li commented on HDFS-5316:
----------------------------------
I've committed the patch. Thank you, Haohui, for the contribution!
> 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
> Assignee: Haohui Mai
> Priority: Critical
> Fix For: 2.2.1
>
> Attachments: HDFS-5316.000.patch
>
>
> 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)
