[HDFS-2264] NamenodeProtocol has the wrong value for clientPrincipal in KerberosInfo annotation

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.2-alpha
• Fix Version/s: 2.0.3-alpha, 1.3.0
• Component/s: namenode
• Target Version/s: 2.0.3-alpha
• Hadoop Flags: Reviewed
• Assignee: Aaron Myers
• Reporter: Aaron Myers
• Created: 17/Aug/11 02:18
• Updated: 22/Jan/14 21:10
• Resolved: 11/Dec/12 00:55

Description

The @KerberosInfo annotation specifies the expected server and client principals for a given protocol in order to look up the correct principal name from the config. The NamenodeProtocol has the wrong value for the client config key. This wasn't noticed because most setups actually use the same value for for both the NN and 2NN principals (hdfs/_HOST@REALM), in which the _HOST part gets replaced at run-time. This bug therefore only manifests itself on secure setups which explicitly specify the NN and 2NN principals.

Issue Links

• duplicates: HDFS-3403 SecondaryNamenode doesn't start up in secure cluster
• is duplicated by: HDFS-3345 Primary and secondary NameNode principals must be the same
• is duplicated by: HDFS-4081 NamenodeProtocol and other Secure Protocols should use different config keys for serverPrincipal and clientPrincipal KerberosInfo components