[
https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197962#comment-14197962
]
Hadoop QA commented on HDFS-7359:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12679492/HDFS-7359.1.patch
against trunk revision 73e6012.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.web.TestWebHDFS
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/8655//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8655//console
This message is automatically generated.
> NameNode in secured HA cluster fails to start if
> dfs.namenode.secondary.http-address cannot be interpreted as a network
> address.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-7359
> URL: https://issues.apache.org/jira/browse/HDFS-7359
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-7359.1.patch
>
>
> In a secured cluster, the JournalNode validates that the caller is one of a
> valid set of principals. One of the principals considered is that of the
> SecondaryNameNode. This involves checking
> {{dfs.namenode.secondary.http-address}} and trying to interpret it as a
> network address. If a user has specified a value for this property that
> cannot be interpeted as a network address, such as "null", then this causes
> the JournalNode operation to fail, and ultimately the NameNode cannot start.
> The JournalNode should not have a hard dependency on
> {{dfs.namenode.secondary.http-address}} like this. It is not typical to run
> a SecondaryNameNode in combination with JournalNodes. There is even a check
> in SecondaryNameNode that aborts if HA is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
