hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3403) SecondaryNamenode doesn't start up in secure cluster
Date Wed, 10 Oct 2012 01:38:02 GMT

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

Aaron T. Myers commented on HDFS-3403:

This looks to me like a duplicate of HDFS-2264. Please see the discussion there for why changing
the expected clientPrincipal for the whole NamenodeProtocol is not reasonable.

I think we should close this JIRA as a duplicate. Do you agree, 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, 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

View raw message