hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brahma Reddy Battula (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4043) Namenode Kerberos Login does not use proper hostname for host qualified hdfs principal name.
Date Mon, 15 Oct 2012 04:35:04 GMT

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

Brahma Reddy Battula commented on HDFS-4043:

Hi Ahad,
thanks for reply..
Have you verified that
the generated service principal name does not match the one stored in your
kdc's database ?

generated principal is HTTP/hostname which is not added in the KDC(I mean not stored in kdc
database) and not configured.. 

> Namenode Kerberos Login does not use proper hostname for host qualified hdfs principal
> --------------------------------------------------------------------------------------------
>                 Key: HDFS-4043
>                 URL: https://issues.apache.org/jira/browse/HDFS-4043
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.0.0-alpha, 2.0.1-alpha, 2.0.2-alpha, 2.0.3-alpha
>         Environment: CDH4U1 on Ubuntu 12.04
>            Reporter: Ahad Rana
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> The Namenode uses the loginAsNameNodeUser method in NameNode.java to login using the
hdfs principal. This method in turn invokes SecurityUtil.login with a hostname (last parameter)
obtained via a call to InetAddress.getHostName. This call does not always return the fully
qualified host name, and thus causes the namenode to login to fail due to kerberos's inability
to find a matching hdfs principal in the hdfs.keytab file. Instead it should use InetAddress.getCanonicalHostName.
This is consistent with what is used internally by SecurityUtil.java to login in other services,
such as the DataNode. 

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

View raw message