[
https://issues.apache.org/jira/browse/HDFS-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795713#comment-16795713
]
CR Hota commented on HDFS-13972:
--------------------------------
[~surendrasingh]
In the case of OPEN/APPEND etc, clients are redirected to datanode and datanode
then connects to router back for operation. Routers are the issuer of the
delegation token.
But for CREATE, since the first redirect is to the appropriate namenode, router
has to try and create delegation token for the namenode. This has 2 issues, one
clients will be able to get details of downstream namenode along with
delegation token for that namenode exposing details of how federation is
set-up, second this flow creates 2 redirects (instead of one) which is
inefficient.
I think router should send back a redirect to datanode (instead of namenode)
for CREATE calls with router's address and DT itself. This needs fundamental
change in how "create" works in router web.
> RBF: Support for Delegation Token (WebHDFS)
> -------------------------------------------
>
> Key: HDFS-13972
> URL: https://issues.apache.org/jira/browse/HDFS-13972
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Íñigo Goiri
> Assignee: CR Hota
> Priority: Major
> Attachments: HDFS-13972-HDFS-13891.001.patch,
> HDFS-13972-HDFS-13891.002.patch, HDFS-13972-HDFS-13891.003.patch,
> HDFS-13972-HDFS-13891.004.patch, HDFS-13972-HDFS-13891.005.patch,
> HDFS-13972-HDFS-13891.006.patch, HDFS-13972-HDFS-13891.007.patch,
> HDFS-13972-HDFS-13891.008.patch, HDFS-13972-HDFS-13891.009.patch,
> TestRouterWebHDFSContractTokens.java
>
>
> HDFS Router should support issuing HDFS delegation tokens through WebHDFS.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
