You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Benoy Antony (JIRA)" <ji...@apache.org> on 2012/05/10 02:36:51 UTC
[jira] [Commented] (HADOOP-8380) SecondaryNamenode doesn't start up
in secure cluster
[ https://issues.apache.org/jira/browse/HADOOP-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271985#comment-13271985 ]
Benoy Antony commented on HADOOP-8380:
--------------------------------------
The error seen on NN indicates that the NN incorrectly requires SNN to authenticate with NN's principal.
> SecondaryNamenode doesn't start up in secure cluster
> ----------------------------------------------------
>
> Key: HADOOP-8380
> URL: https://issues.apache.org/jira/browse/HADOOP-8380
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: security
> Affects Versions: 0.22.0
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Priority: Minor
> Fix For: 0.22.1
>
> Attachments: incorrect-sn-principal.patch
>
>
> SN fails to startup due to access control error. This is an authorization issue and not authentication issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira