[ https://issues.apache.org/jira/browse/HADOOP-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469779#comment-13469779 ]
Arpit Gupta commented on HADOOP-8878: ------------------------------------- Here is the output of test patch for branch 1 {code} [exec] -1 overall. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 2 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] -1 findbugs. The patch appears to introduce 9 new Findbugs (version 1.3.9) warnings. [exec] [exec] {code} Findbugs warnings are unrelated to this patch. > 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.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