Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 16 Apr 2012 21:48:20 +0000 (UTC)
From: "Todd Lipcon (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <516328807.30568.1334612900283.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1853493169.29534.1334600420226.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure
 cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon commented on HDFS-3284:
-----------------------------------

The test failure is unrelated (this patch doesn't touch that area of the code)
                
> bootstrapStandby fails in secure cluster
> ----------------------------------------
>
>                 Key: HDFS-3284
>                 URL: https://issues.apache.org/jira/browse/HDFS-3284
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, security
>    Affects Versions: 2.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>         Attachments: hdfs-3284.txt, hdfs-3284.txt
>
>
> HDFS-3247 improved bootstrapStandby to check if the other NN is in active state before trying to bootstrap. But, it forgot to set up the kerberos principals in the config before doing so. So, bootstrapStandby now fails with "Failed to specify server's Kerberos principal name" in a secure cluster. (Credit to Stephen Chu for finding this)

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