You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Arpit Gupta (JIRA)" <ji...@apache.org> on 2012/10/04 18:39:47 UTC

[jira] [Commented] (HADOOP-8878) uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on

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

Arpit Gupta commented on HADOOP-8878:
-------------------------------------

This would also impact fsck as it goes through the same code path.

@Dayrn i will take a look and see what can be done to add the ability to write a test for it.
                
> uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8878
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8878
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 1.0.3, 1.1.0, 1.2.0, 3.0.0
>            Reporter: Arpit Gupta
>            Assignee: Arpit Gupta
>         Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.patch
>
>
> This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued
> hadoop dfs -ls webhdfs://NN:PORT/PATH
> the above command failed because delegation token retrieval failed.
> Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class.
> I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly.

--
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