hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5272) DFSUtil#getInfoServer cleanup
Date Sun, 06 Oct 2013 19:09:43 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787742#comment-13787742
] 

Haohui Mai commented on HDFS-5272:
----------------------------------

HDFS-5312 should cover this. Marking this as a 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)

Mime
View raw message