[
https://issues.apache.org/jira/browse/HDFS-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129535#comment-14129535
]
Yongjun Zhang commented on HDFS-7036:
-------------------------------------
Hi [~wheat9] and [~jingzhao],
Thanks for the discussion in HDFS-6776.
I described the two proposed solutions for addressing HDFS-7036 in the jira
description. I think adding the msg-parsing hack in webhdfs seems to be the
right approach so we don't have to put the similar hack in different
applications. For example, even "hadoop fs -lsr webhdfs://<insecureCluster>" is
broken for the same reason.
The argument against this approach was, the webhdfs has a large audience, thus
could be an overkill. Would you please provide some more detail here?
Assuming that we don't put the hack in webhdfs, would you please share some
thoughts about the right solution?
Thanks a lot.
> HDFS-6776 fix requires to upgrade insecure cluster, which means quite some
> user pain
> ------------------------------------------------------------------------------------
>
> Key: HDFS-7036
> URL: https://issues.apache.org/jira/browse/HDFS-7036
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Reporter: Yongjun Zhang
> Assignee: Yongjun Zhang
>
> Issuing command
> {code}
> hadoop fs -lsr webhdfs://<insecureCluster>
> {code}
> at a secure cluster side fails with message "Failed to get the token ...",
> similar symptom as reported in HDFS-6776.
> If the fix of HDFS-6776 is applied to only the secure cluster, doing
> {code}
> distcp webhdfs://<insecureCluster> <secureCluster>
> {code}
> would fail same way.
> Basically running any application in secure cluster to access insecure
> cluster via webhdfs would fail the same way, if the HDFS-6776 fix is not
> applied to the insecure cluster.
> This could be quite some user pain. Filing this jira for a solution to make
> user's life easier.
> One proposed solution was to add a msg-parsing mechanism in webhdfs, which is
> a bit hacky. The other proposed solution is to do the same kind of hack at
> application side, which means the same hack need to be applied in each
> application.
> Thanks [~daryn], [~wheat9], [~jingzhao], [~tucu00] and [~atm] for the
> discussion in HDFS-6776.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
