[ https://issues.apache.org/jira/browse/HDFS-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042858#comment-14042858 ]
Aaron T. Myers commented on HDFS-5321: -------------------------------------- Hey folks, sorry to come into this JIRA late, but I'm a bit concerned about making this incompatible change in a minor release. I fully realize that the functionality is still there if users rewrite their applications or URIs to include the non-default port, but why do we think that's a reasonable change to require upon a minor version upgrade? > 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 > Fix For: 2.4.0 > > Attachments: HDFS-5321.000.patch, HDFS-5321.001.patch > > > 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.2#6252)