[HDFS-6273] Config options to allow wildcard endpoints for namenode HTTP and HTTPS servers

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.5.0
• Component/s: namenode
• Target Version/s: 2.5.0
• Hadoop Flags: Reviewed

Release Note

HDFS-6273 introduces two new HDFS configuration keys:
- 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

• Assignee: Arpit Agarwal
• Reporter: Arpit Agarwal
• Created: 23/Apr/14 03:47
• Updated: 16/Apr/18 22:16
• Resolved: 24/Apr/14 17:44

Description

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:

1. dfs.namenode.rpc-bind-host
2. dfs.namenode.servicerpc-address

This Jira is to add similar options for the HTTP and HTTPS endpoints.

Issue Links

• is related to: HDFS-3150 Add option for clients to contact DNs via hostname
• is related to: HDFS-5128 Allow multiple net interfaces to be used with HA namenode RPC server
• relates to: HDFS-13462 Add BIND_HOST configuration for JournalNode's HTTP and RPC Servers
• relates to: YARN-1994 Expose YARN/MR endpoints on multiple interfaces