hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (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 18:39:34 GMT

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

Jing Zhao commented on HDFS-7359:
---------------------------------

Thanks for the update, Chris! 

For ImageServlet I have a question. Because ImageServlet is also used by Secondary NN for
checkpointing. With the change in v2 is it possible that we can no longer detect wrong configuration
for SNN during the startup?

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