Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6C3A8103E4 for ; Wed, 23 Apr 2014 03:53:18 +0000 (UTC) Received: (qmail 22744 invoked by uid 500); 23 Apr 2014 03:53:16 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 22596 invoked by uid 500); 23 Apr 2014 03:53:15 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 22588 invoked by uid 99); 23 Apr 2014 03:53:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2014 03:53:14 +0000 Date: Wed, 23 Apr 2014 03:53:14 +0000 (UTC) From: "Arpit Agarwal (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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. If the {{DFS_NAMENODE_HTTP_ADDRESS_KEY}} or {{DFS_NAMENODE_HTTPS_ADDRESS_KEY}} key is used 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 (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)