[HDFS-7036] HDFS-6776 fix requires to upgrade insecure cluster, which means quite some user pain

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.5.1
• Component/s: webhdfs
• Labels: BB2015-05-TBR
• Assignee: Yongjun Zhang
• Reporter: Yongjun Zhang
• Created: 10/Sep/14 05:56
• Updated: 06/May/15 03:28

Description

Issuing command

 hadoop fs -lsr webhdfs://<insecureCluster>

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

distcp webhdfs://<insecureCluster> <secureCluster>

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.