[
https://issues.apache.org/jira/browse/HDFS-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978507#comment-13978507
]
Suresh Srinivas commented on HDFS-6273:
---------------------------------------
+1 for the patch.
Minor nit: instead of adding check for new config in #startHttpServer(), you
can make the change in NameNode#getHttpAddress(). This keeps startHttpServer()
concise. That said, I am okay if you want to retain the existing code.
> Option to allow wildcard endpoints for namenode HTTP and HTTPS servers
> ----------------------------------------------------------------------
>
> Key: HDFS-6273
> URL: https://issues.apache.org/jira/browse/HDFS-6273
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.4.0
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Attachments: HDFS-6273.01.patch
>
>
> The NameNode already has a couple of keys to allow the RPC and Service RPC
> servers to bind the wildcard address (0.0.0.0) which is useful in multihomed
> environments via:
> # {{dfs.namenode.rpc-bind-host}}
> # {{dfs.namenode.servicerpc-address}}
> This Jira is to add similar options for the HTTP and HTTPS endpoints.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
