[
https://issues.apache.org/jira/browse/MAPREDUCE-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659730#comment-13659730
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-5199:
----------------------------------------------------
Looking at the patch. But I don't understand the problem, but not discounting
that there isn't any problem at all.
bq. MAPREDUCE-5205 fixed the AM to pick up the app token, but jobs launching
jobs (ex. oozie) still fail. The child job reads in the appTokens file
generated by the parent job which causes the child to overwrite the app token
with that of the parent job.
I don't understand this. AMRMToken is never part of the appTokens files. Where
is the child job failing? Can you share some exception traces?
> 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
