[
https://issues.apache.org/jira/browse/HDFS-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haohui Mai resolved HDFS-5272.
------------------------------
Resolution: Duplicate
> DFSUtil#getInfoServer cleanup
> -----------------------------
>
> Key: HDFS-5272
> URL: https://issues.apache.org/jira/browse/HDFS-5272
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0
> Reporter: Arpit Agarwal
> Assignee: Haohui Mai
>
> The {{httpsAddress}} parameter is not used outside of tests.
> {code}
> public static String getInfoServer(InetSocketAddress namenodeAddr,
> Configuration conf, boolean httpsAddress) throws IOException {
> boolean securityOn = UserGroupInformation.isSecurityEnabled();
> String httpAddressKey = (securityOn && httpsAddress) ?
> DFS_NAMENODE_HTTPS_ADDRESS_KEY : DFS_NAMENODE_HTTP_ADDRESS_KEY;
> String httpAddressDefault = (securityOn && httpsAddress) ?
> DFS_NAMENODE_HTTPS_ADDRESS_DEFAULT :
> DFS_NAMENODE_HTTP_ADDRESS_DEFAULT;
> {code}
> [~jingzhao] confirmed on HDFS-5271 that DFS_NAMENODE_HTTP_ADDRESS_DEFAULT
> will be the default that is always available so there should be no reason to
> choose betwen DFS_NAMENODE_HTTP_ADDRESS_DEFAULT and
> DFS_NAMENODE_HTTPS_ADDRESS_DEFAULT. Filing Jira to clean this up.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
