[
https://issues.apache.org/jira/browse/MAPREDUCE-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663509#comment-13663509
]
Daryn Sharp commented on MAPREDUCE-5199:
----------------------------------------
Yes, this most certainly is still a blocker. Our 2.x oozie testing is blocked.
Oozie launcher in uber-AM mode definitely causes the problem by putting the UGI
token file path into the job submission. Oozie also reports, although I
haven't seen the logs, that it fails the same way when not uber. I saw the app
token in pi jobs.
Removing the appTokens file prevents a leaked app token from squashing the app
token in the child AM. I too want to ensure we definitively find the root
issue, but that should be another jira and/or offline investigation.
> 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
