You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Haohui Mai (JIRA)" <ji...@apache.org> on 2013/10/08 00:49:41 UTC
[jira] [Created] (HDFS-5321) Clean up the HTTP-related
configuration in HDFS
Haohui Mai created HDFS-5321:
--------------------------------
Summary: Clean up the HTTP-related configuration in HDFS
Key: HDFS-5321
URL: https://issues.apache.org/jira/browse/HDFS-5321
Project: Hadoop HDFS
Issue Type: Sub-task
Reporter: Haohui Mai
Assignee: Haohui Mai
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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)