[
https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-3284:
------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.
> 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
> Fix For: 2.0.0
>
> 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
