[
https://issues.apache.org/jira/browse/HDFS-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788763#comment-13788763
]
Brandon Li commented on HDFS-5321:
----------------------------------
dfs.https.port and dfs.http.port are already deprecated (referring
HdfsConfiguration#addDeprecatedKeys).
We can use this JIRA to improve the hdfs-site.xml document to clearly describe
the relationship among these configurations. For example, what happens when
both dfs.namenode.https-address and dfs.https.port are configured.
> 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)
