[ https://issues.apache.org/jira/browse/HDFS-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526703#comment-13526703 ]
Aaron T. Myers commented on HDFS-2264: -------------------------------------- The test failure was unrelated and was fixed by HDFS-4282. No tests are included in this patch since Kerberos is required to test this stuff out. Daryn, how does this patch look now? > 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 > Attachments: 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira