[jira] [Commented] (HDFS-5321) Clean up the HTTP-related configuration in HDFS

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915253#comment-13915253 ] 

Hadoop QA commented on HDFS-5321:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12631600/HDFS-5321.000.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6261//console

This message is automatically generated.

> 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
>         Attachments: HDFS-5321.000.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.1.5#6160)