[
https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721403#comment-13721403
]
Alejandro Abdelnur commented on YARN-937:
-----------------------------------------
{{getRMCurrentAddress()}}, we would have to pass the config and a more
appropriate name would be {{getRMSchedulerAddress()}}.
Also, shouldn't be the {{ApplicationClientProtocol}} instance the one returning
the address?
And this seems like it will affect other things as well. I think we should take
care of this in another JIRA.
Are you OK on committing the current patch and following up with another JIRA
(making it a blocker for the release after 2.1.0)?
> 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, YARN-937.patch, YARN-937.patch,
> YARN-937.patch, YARN-937.patch, 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
