[
https://issues.apache.org/jira/browse/HDFS-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451003#comment-13451003
]
Hadoop QA commented on HDFS-3905:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12544294/HDFS-3905.patch
against trunk revision .
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3159//console
This message is automatically generated.
> 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
> 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
