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 "Benoy Antony (JIRA)" <ji...@apache.org> on 2012/10/09 21:00:03 UTC
[jira] [Reopened] (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 ]
Benoy Antony reopened HDFS-3403:
--------------------------------
Reopening this issue as it is found on Hadoop 1.1 as well.
> 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
> 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