[
https://issues.apache.org/jira/browse/HADOOP-10016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786727#comment-13786727
]
Sanjay Radia commented on HADOOP-10016:
---------------------------------------
Context:
* Copying data from Secure 2.x to Insecure 2.x works because of rpc v9 (the
reverse, I think will also works).
* Want to copy data via DistCp from insecure 1.x to Secure 2.x - this does not
work - the issue is similar to the next one.
* Want to copy data via DistCp from secure 1.x to insecure 2.x - this fails
as described below.
Currently an insecure cluster returns *null* for getDelegationToken(). 2.x
clients do freakout on this null token but this is fixed by Hadoop-10017. But
the key problem is as follows.
* Distcp job runs in Secure1.x cluster, and it tries connect to NN in
Insecure2.x.
* Because security is enabled (distcp is running in Secure1.x cluster), it
sees that it has no tokens for that cluster (recall none were obtained because
a null was returned); then it tries to do a kerberos based authentication; this
fails because it has no kerberos credentials (it is running as a MR job) - even
the fallback to insecure does not work because it fails *before* the
RPC-connection.
Solution - have the NN in Insecure2.x return an artificial-token.
> Distcp should support copy from a secure Hadoop 1 cluster to an insecure
> Hadoop 2 cluster
> -----------------------------------------------------------------------------------------
>
> Key: HADOOP-10016
> URL: https://issues.apache.org/jira/browse/HADOOP-10016
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Haohui Mai
> Assignee: Haohui Mai
>
> Distcp should be able to copy from a secure cluster to an insecure cluster.
> This functionality is important for operators to migrate data to a new Hadoop
> installation.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
