[
https://issues.apache.org/jira/browse/HDFS-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDFS-6273:
--------------------------------
Release Note:
Two new HDFS configuration keys have been introduced by HDFS-6273.
- dfs.namenode.http-bind-host
- dfs.namenode.https-bind-host
The most common use case for these keys is to have the NameNode HTTP (or HTTPS)
endpoints listen on all interfaces on multi-homed systems by setting the keys
to 0.0.0.0 i.e. INADDR_ANY.
For the systems background on this usage of INADDR_ANY please refer to ip(7) in
the Linux Programmer's Manual (web link:
http://man7.org/linux/man-pages/man7/ip.7.html).
These keys complement the existing NameNode options:
- dfs.namenode.rpc-bind-host
- dfs.namenode.servicerpc-bind-host
I added a release note describing the intended use case for these options.
> Config options 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
> Fix For: 3.0.0, 2.5.0
>
> Attachments: HDFS-6273.01.patch, HDFS-6273.02.patch,
> HDFS-6273.03.patch, HDFS-6273.04.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)
