hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4713) Wrong server principal is used for rpc calls to namenode if HA is enabled
Date Mon, 22 Apr 2013 21:29:15 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638448#comment-13638448
] 

Kihwal Lee commented on HDFS-4713:
----------------------------------

It works by using "user@/_HOST@relm" as principal. But then what's the point of having dfs.namenode.kerberosprincipal.<nsid>.<nnid>?
Since there is a workaround, I will lower the priority.
                
> 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
>            Priority: Blocker
>
> 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

Mime
View raw message