[HDFS-3403] SecondaryNamenode doesn't start up in secure cluster

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 0.22.0, 1.1.0, 2.0.3-alpha
• Fix Version/s: 0.22.1
• Component/s: security
• Hadoop Flags: Reviewed
• Assignee: Benoy Antony
• Reporter: Benoy Antony
• Created: 09/May/12 23:46
• Updated: 10/Oct/12 05:29
• Resolved: 10/Oct/12 05:27

Description

SN fails to startup due to access control error. This is an authorization issue and not authentication issue.

Issue Links

• is depended upon by: HADOOP-8357 Restore security in Hadoop 0.22 branch
• is duplicated by: HDFS-2264 NamenodeProtocol has the wrong value for clientPrincipal in KerberosInfo annotation