[HDFS-5321] Clean up the HTTP-related configuration in HDFS

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.4.0
• Hadoop Flags: Incompatible change, Reviewed

Release Note

dfs.http.port and dfs.https.port are removed. Filesystem clients, such as WebHdfsFileSystem, now have fixed instead of configurable default ports (i.e., 50070 for http and 50470 for https).

Users can explicitly specify the port in the URI to access the file system which runs on non-default ports.

• Assignee: Haohui Mai
• Reporter: Haohui Mai
• Created: 07/Oct/13 22:48
• Updated: 19/Dec/19 12:17
• Resolved: 05/Mar/14 00:56

Description

Currently there are multiple configuration keys that control the ports that the NameNode and DataNode listen to, and the default ports that the hftp/webhdfs clients are connecting to.

Below is a quick summary of these configuration:

Keys	Description
dfs.namenode.http-address	The address that the namenode http server binds to
dfs.namenode.https-address	The address that the namenode https server binds to
dfs.http.port	The default port that the hftp/webhdfs client use to connect to the remote server
dfs.https.port	The default port that the hsftp client use to connect to the remote server

I propose to deprecate dfs.http.port and dfs.https.port to avoid potential confusions (e.g., HDFS-5316). Note that this removes no functionality, since the users can specify ports in hftp / webhdfs URLs when they need to connect to HDFS servers with non-default ports.

Issue Links

• relates to: HDFS-6632 Reintroduce dfs.http.port / dfs.https.port in branch-2
• supercedes: HDFS-2585 dfs.https.port is a bit confusing