hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7359) NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.
Date Wed, 05 Nov 2014 23:23:34 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199348#comment-14199348
] 

Hudson commented on HDFS-7359:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #6457 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/6457/])
HDFS-7359. NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address
cannot be interpreted as a network address. Contributed by Chris Nauroth. (cnauroth: rev ba1d4ad25b301f7247f3f23df15e7f800e50feed)
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/qjournal/TestSecureNNWithQJM.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/server/GetJournalEditServlet.java
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/qjournal/TestNNWithQJM.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ImageServlet.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt


> 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, HDFS-7359.2.patch, HDFS-7359.3.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)

Mime
View raw message