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] [Updated] (HDFS-6273) Config options to allow wildcard endpoints for namenode HTTP and HTTPS servers
Date Thu, 24 Apr 2014 17:45:18 GMT

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

Arpit Agarwal updated HDFS-6273:
--------------------------------

          Resolution: Fixed
       Fix Version/s: 2.5.0
                      3.0.0
    Target Version/s: 2.5.0
        Hadoop Flags: Reviewed
              Status: Resolved  (was: Patch Available)

I committed this to trunk and branch-2.

> Config options 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
>             Fix For: 3.0.0, 2.5.0
>
>         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