NamenodeProtocol has the wrong value for clientPrincipal in KerberosInfo
annotation
-----------------------------------------------------------------------------------
Key: HDFS-2264
URL: https://issues.apache.org/jira/browse/HDFS-2264
Project: Hadoop HDFS
Issue Type: Bug
Components: name-node
Affects Versions: 0.23.0
Reporter: Aaron T. Myers
Assignee: Aaron T. Myers
Fix For: 0.23.0
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
