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 Wed, 23 Apr 2014 03:53:14 GMT

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

Arpit Agarwal commented on HDFS-6273:

These endpoints do bind the wildcard address by default but this is only useful in test clusters.
as is common in real clusters then the ability to use the wildcard address is lost. This can
be fixed by adding new options that override only the hostname portion of the HTTP and HTTPS
address keys, similar to the existing approach for the RPC and service RPC endpoints.

A similar fix is possible for the DataNode but unlikely to be useful since the DataNode already
binds the wildcard address by default for all RPC and HTTP endpoints and these defaults are
not usually overriden.

> 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
> The NameNode already has a couple of keys to allow the RPC and Service RPC servers to
bind the wildcard address ( 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

View raw message