[
https://issues.apache.org/jira/browse/HDFS-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639254#comment-13639254
]
Daryn Sharp commented on HDFS-4713:
-----------------------------------
The only use case I can see for different keys is if the NNs are running as
different users. However the current implementation doesn't support that. It
assumes any remote NN's principal can be constructed via its own configured
principal, so yes, use of _HOST is currently mandatory.
> Wrong server principal is used for rpc calls to namenode if HA is enabled
> -------------------------------------------------------------------------
>
> Key: HDFS-4713
> URL: https://issues.apache.org/jira/browse/HDFS-4713
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
> Affects Versions: 2.0.5-beta
> Reporter: Kihwal Lee
>
> When various components are connecting to a namenode in a HA-enabled
> environment, a wrong server principal may be picked up. This result in SASL
> failure, since the client-side used a wrong service ticket for the connection.
--
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
