hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5321) Clean up the HTTP-related configuration in HDFS
Date Thu, 27 Feb 2014 21:17:22 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Haohui Mai updated HDFS-5321:
-----------------------------

    Target Version/s:   (was: )
              Status: Patch Available  (was: Open)

> 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)

Mime
View raw message