hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8878) uppercase namenode hostname causes hadoop dfs calls with webhdfs filesystem and fsck to fail when security is on
Date Thu, 11 Oct 2012 06:41:03 GMT

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

Suresh Srinivas updated HADOOP-8878:
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.3-alpha
                   1.2.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

+1 for the patch. I committed it to trunk , branch-2 and branch-1. Thank you Arpit.
                
> 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
>             Fix For: 1.2.0, 2.0.3-alpha
>
>         Attachments: HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch, HADOOP-8878.branch-1.patch,
HADOOP-8878.patch, HADOOP-8878.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

Mime
View raw message