[
https://issues.apache.org/jira/browse/MAPREDUCE-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660039#comment-13660039
]
Siddharth Seth commented on MAPREDUCE-5199:
-------------------------------------------
Daryn, I'd looked at the AM code a couple of days ago as part of our offline
conversation. I'm still not sure how the AppToken gets clobbered in the Task.
From looking at the AM code, it doesn't look like the CLC for the Task (Oozie
launcher map task) gets anything from the AM's ugi. It only gets the job token
generated by the AM, and the tokens from the 'appTokens' file. This file is
written out by the client - at which point the AMToken is not available.
Has Oozie, by any chance, changed to launch it's tasks via an AM itself (which
has similar ugi magic as the MR AM)?
> AppTokens file can/should be removed
> ------------------------------------
>
> Key: MAPREDUCE-5199
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5199
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: security
> Affects Versions: 3.0.0, 2.0.5-beta
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Daryn Sharp
> Priority: Blocker
> Attachments: MAPREDUCE-5199.patch
>
>
> All the required tokens are propagated to AMs and containers via
> startContainer(), no need for explicitly creating the app-token file that we
> have today..
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
