Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Fri, 4 May 2012 18:28:47 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: 
 <810771357.28220.1336156127834.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <423919076.15454.1335916012385.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HDFS-3345) Primary and secondary NameNode
 principals must be the same
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aaron T. Myers resolved HDFS-3345.
----------------------------------

    Resolution: Duplicate

Closing this as a dupe. Please feel free to reopen it if you disagree, or if I've misinterpreted your report of the issue.
                
> Primary and secondary NameNode principals must be the same
> ----------------------------------------------------------
>
>                 Key: HDFS-3345
>                 URL: https://issues.apache.org/jira/browse/HDFS-3345
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Owen O'Malley
>
> The NameNode and SecondaryNameNode have two different configuration knobs (dfs.namenode.kerberos.principal and dfs.secondary.namenode.kerberos.principal), but the secondary namenode fails authorization unless it is the same user.

--
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