hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6273) Option to allow wildcard endpoints for namenode HTTP and HTTPS servers
Date Thu, 24 Apr 2014 08:03:17 GMT

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

Arpit Agarwal commented on HDFS-6273:
-------------------------------------

bq. Seems like this is not useless. Its creating "port in use" errors in BackUpNode tests
as both NN and BNN are trying to start in same HTTP ports.
Yes you are right, the latest patch addresses that. Thanks.

> Option to allow wildcard endpoints for namenode HTTP and HTTPS servers
> ----------------------------------------------------------------------
>
>                 Key: HDFS-6273
>                 URL: https://issues.apache.org/jira/browse/HDFS-6273
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.4.0
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>         Attachments: HDFS-6273.01.patch, HDFS-6273.02.patch, HDFS-6273.03.patch, HDFS-6273.04.patch
>
>
> The NameNode already has a couple of keys to allow the RPC and Service RPC servers to
bind the wildcard address (0.0.0.0) which is useful in multihomed environments via:
> # {{dfs.namenode.rpc-bind-host}}
> # {{dfs.namenode.servicerpc-address}}
> This Jira is to add similar options for the HTTP and HTTPS endpoints.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message