[
https://issues.apache.org/jira/browse/HDFS-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131670#comment-14131670
]
Yongjun Zhang commented on HDFS-7036:
-------------------------------------
Hi [~wheat9] and [~jingzhao],
I agree with [~tucu00] that this is a quite important thing to do to help user:
{quote}
IMO it will be a pita for users with multiple clusters the fact that we are not
parsing the exception message. Please lets have a follow up JIRA for it.
{quote}
Not sure whether you have time to comment soon. To establish a base for further
discussion, I uploaded the similar approach (rev 001 here) we proposed earlier
in HDFS-6776. I'd really appreciate if you guys can comment and we can converge
to a solution.
BTW, since the IOException("Failed to get the token .." ) is now removed by
HDFS-6776, I didn't introduce a string constant for that. The msg parsed by rev
001 is the sole occurence.
Thanks.
> 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
> Affects Versions: 2.5.1
> Reporter: Yongjun Zhang
> Assignee: Yongjun Zhang
> Attachments: HDFS-7036.001.patch
>
>
> 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)
