[ https://issues.apache.org/jira/browse/HDFS-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jing Zhao updated HDFS-2264: ---------------------------- Attachment: HDFS-2264.b1.patch Backport to branch-1. > 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: namenode > Affects Versions: 2.0.2-alpha > Reporter: Aaron T. Myers > Assignee: Aaron T. Myers > Fix For: 2.0.3-alpha > > Attachments: HDFS-2264.b1.patch, HDFS-2264.patch, HDFS-2264.patch, > HDFS-2264.r1.diff > > > 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 was sent by Atlassian JIRA (v6.1#6144)