[
https://issues.apache.org/jira/browse/MAPREDUCE-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662357#comment-13662357
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-5199:
----------------------------------------------------
I just finished another test with debug-delete-delays and wait times: None of
the tasks' files - appTokens, containerTokens, appId.tokens files have any of
ApplicationTokens for tasks. They are only present in the AM's files.
So, back to square one, no idea why oozie workflows would fail.
That said, this patch can go in anyways and if it somehow fixes your issue,
great.
There are couple of other solutions to avoid tasks using the wrong token for
the AM-RM connection - like fixing the TokenSelector, but we can pursue that
separately to unblock you.
Will review the patch in a little while.
> 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
