[
https://issues.apache.org/jira/browse/HDFS-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HDFS-3905:
------------------------------
Attachment: HDFS-3905.patch
Try to acquire the service ticket. If it fails, save the exception. Try to
connect to the secure port anyway since the cluster might be insecure. If the
connect fails, throw it since it's insecure. If the connect succeeds but fails
to negotiate, throw the exception acquiring the TGS if one occurred.
> 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
