[
https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated YARN-937:
------------------------------------
Attachment: YARN-937.patch
Patch that adds to the YarnClient a method to retrieve the AMRM token from an
application (giving an appId).
The AMRM token is only returned when:
* the AM is unmanaged
* the AM is owned by the current user
* the AM is RUNNING
testcases verifies the first 2 conditions, the last condition cannot be
verified easily.
I've also verified that this patch fixed my unmanaged AM.
The {{TestUnnmanagedAMLauncher}} is still commented out because the
{{UnmanagedAMLauncher}} requires additional work (it launches a different JVM,
and we need to propagate the tokens to it). I'll open a JIRA to fix this.
> Fix unmanaged AM in non-secure/secure setup post YARN-701
> ---------------------------------------------------------
>
> Key: YARN-937
> URL: https://issues.apache.org/jira/browse/YARN-937
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-beta
> Reporter: Arun C Murthy
> Assignee: Alejandro Abdelnur
> Priority: Blocker
> Fix For: 2.1.0-beta
>
> Attachments: YARN-937.patch
>
>
> Fix unmanaged AM in non-secure/secure setup post YARN-701 since app-tokens
> will be used in both scenarios.
--
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
