[
https://issues.apache.org/jira/browse/HDFS-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978963#comment-13978963
]
Hadoop QA commented on HDFS-6273:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12641533/HDFS-6273.02.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6706//console
This message is automatically generated.
> 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
>
>
> 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)
