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

Posted to hdfs-dev@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2012/06/05 04:56:23 UTC

[jira] [Resolved] (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:all-tabpanel ]

Konstantin Shvachko resolved HDFS-3403.
---------------------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed

+1
I just committed this to branch 0.22.1. Thank you Benoy.
                
> 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
>            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