You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Kihwal Lee (JIRA)" <ji...@apache.org> on 2013/04/24 21:51:16 UTC

[jira] [Resolved] (HDFS-4713) Wrong server principal is used for rpc calls to namenode if HA is enabled

     [ https://issues.apache.org/jira/browse/HDFS-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kihwal Lee resolved HDFS-4713.
------------------------------

    Resolution: Won't Fix

By requiring "_HOST" to be used, we rely on the rpc server address to guess the server principal. This is fine as long as all use cases can be supported.  The ability to set separate principal for each namenode in HA config can be misleading, but does not hurt. Resolving as "won't fix".
                
> 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