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 "Hudson (JIRA)" <ji...@apache.org> on 2012/06/05 12:26:23 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=13289313#comment-13289313 ]
Hudson commented on HDFS-3403:
------------------------------
Integrated in Hadoop-Hdfs-22-branch #131 (See [https://builds.apache.org/job/Hadoop-Hdfs-22-branch/131/])
HDFS-3403. SecondaryNameNode doesn't start up in secure cluster. Contributed by Benoy Antony. (Revision 1346217)
Result = FAILURE
shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1346217
Files :
* /hadoop/common/branches/branch-0.22/hdfs/CHANGES.txt
* /hadoop/common/branches/branch-0.22/hdfs/src/java/org/apache/hadoop/hdfs/server/protocol/NamenodeProtocol.java
> 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