You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Benoy Antony (JIRA)" <ji...@apache.org> on 2012/10/09 21:04:03 UTC

[jira] [Commented] (HDFS-3403) SecondaryNamenode doesn't start up in secure cluster

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

Benoy Antony commented on HDFS-3403:
------------------------------------

The same code is present in trunk as well. So believe it is a bug in 2.0 and trunk as well.
The same patch is applicable in all branches
                
> SecondaryNamenode doesn't start up in secure cluster
> ----------------------------------------------------
>
>                 Key: HDFS-3403
>                 URL: https://issues.apache.org/jira/browse/HDFS-3403
>             Project: Hadoop HDFS
>          Issue Type: Task
>          Components: security
>    Affects Versions: 0.22.0, 1.1.0, 2.0.3-alpha
>            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
For more information on JIRA, see: http://www.atlassian.com/software/jira