[
https://issues.apache.org/jira/browse/MAPREDUCE-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134009#comment-16134009
]
Jian He commented on MAPREDUCE-6838:
------------------------------------
today, for other delegation tokens RMDelegationToken, the old ATSv1
DelegationToken, the token service is not set at server side, it is set at
client side - the client call the SecurityUtils#buildTokenService and then set
the token service. I don't know what it was done like that - maybe because it
avoids the use_ip config inconsistency between client and serve ?
Should we follow the same ? The client can construct the tokenService based on
the collector address info ? (One caveat is to make sure the old token gets
probably replaced properly - in case ip changes ?)
The CollectorInfo#getCollectorAddr right now is a string, should it be an
address type ?
> [ATSv2 Security] Add timeline delegation token received in allocate response
> to UGI
> -----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6838
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6838
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Reporter: Varun Saxena
> Assignee: Varun Saxena
> Labels: yarn-5355-merge-blocker
> Fix For: YARN-5355
>
> Attachments: MAPREDUCE-6838-YARN-5355.01.patch,
> MAPREDUCE-6838-YARN-5355.02.patch, MAPREDUCE-6838-YARN-5355.03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
