hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3905) Secure cluster cannot use hftp to an insecure cluster
Date Thu, 04 Oct 2012 12:43:08 GMT

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

Hudson commented on HDFS-3905:

Integrated in Hadoop-Hdfs-0.23-Build #394 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/394/])
    HDFS-3905. Secure cluster cannot use hftp to an insecure cluster (Daryn Sharp via tgraves)
(Revision 1393699)

     Result = SUCCESS
tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1393699
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DelegationTokenFetcher.java

> Secure cluster cannot use hftp to an insecure cluster
> -----------------------------------------------------
>                 Key: HDFS-3905
>                 URL: https://issues.apache.org/jira/browse/HDFS-3905
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client, security
>    Affects Versions: 0.23.3
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Critical
>             Fix For: 0.23.5
>         Attachments: HDFS-3905.patch
> HDFS-3873 fixed the case where all exceptions acquiring tokens for hftp were ignored.
 Jobs would be submitted sans tokens, and then the tasks would eventually all fail trying
to get the missing token.  HDFS-3873 made jobs fail to submit if the remote cluster is secure.
> Unfortunately it regressed the ability for a secure cluster to access an insecure cluster
over hftp.  The issue is unique to 23 due to KSSL.

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