Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 23 Apr 2014 22:28:22 +0000 (UTC)
From: "Arpit Agarwal (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12709933.1398224852800.167707.1398292102074@arcas>
In-Reply-To: <JIRA.12709933.1398224852800@arcas>
References: <JIRA.12709933.1398224852800@arcas>
Subject: [jira] [Updated] (HDFS-6273) Option to allow wildcard endpoints for
 namenode HTTP and HTTPS servers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

    Attachment: HDFS-6273.03.patch

Updated patch to remove a useless override from the BackupNode. I missed that in my v2 patch.

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