[ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260532#comment-13260532 ]
Hudson commented on HDFS-3312: ------------------------------ Integrated in Hadoop-Mapreduce-trunk #1059 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1059/]) HDFS-3312. In HftpFileSystem, the namenode URI is non-secure but the delegation tokens have to use secure URI. Contributed by Daryn Sharp (Revision 1329462) Result = FAILURE szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1329462 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HftpFileSystem.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HsftpFileSystem.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestHftpDelegationToken.java > Hftp selects wrong token service > -------------------------------- > > Key: HDFS-3312 > URL: https://issues.apache.org/jira/browse/HDFS-3312 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs client > Affects Versions: 0.24.0, 0.23.3, 2.0.0 > Reporter: Daryn Sharp > Assignee: Daryn Sharp > Priority: Blocker > Fix For: 0.23.3 > > Attachments: HDFS-3312.patch > > > Hftp tries to select a token based on the non-secure port in the uri, instead > of the secure-port. This breaks hftp on a secure cluster and there is no > workaround. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira