[
https://issues.apache.org/jira/browse/HDFS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754761#action_12754761
]
Kan Zhang commented on HDFS-592:
--------------------------------
> This is used in both pipeline recovery and setting up the initial pipeline
> for append.
The initial pipeline setup for append should get its access token from the
append() call (like how it is done today). In general, each operation that
requires an access token should get it separately (as part of the return value
of the related RPC call). The namenode needs to know the context in which the
access token will be used before authorizing the client and issuing the token.
That's why there is no generic getAccessToken() call on the ClientProtocol
interface. The authorization requirements for initial pipeline setup for append
may be different from that of pipeline recovery. They should get their tokens
separately (similar to the way addBlock() gets its own tokens to use).
> Allow client to get a new generation stamp from NameNode
> --------------------------------------------------------
>
> Key: HDFS-592
> URL: https://issues.apache.org/jira/browse/HDFS-592
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
> Affects Versions: Append Branch
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: Append Branch
>
> Attachments: newGS.patch, newGS1.patch
>
>
> This issue aims to add an API to ClientProtocol that fetches a new
> generation stamp and an access token from NameNode to support append or
> pipeline recovery.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
