[
https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721228#comment-13721228
]
Alejandro Abdelnur commented on YARN-937:
-----------------------------------------
bq. Since the AMRMToken already has the service field populated we dont need to
override anything. So we dont need to lookup any address from config in the
YARNClient code. Later, for HA if we need to do some translation, then it
should probably happen via the RMProxy layer. Does that work for you?
Well, [~daryn] has been doing lot of work to ensure the service of a token is
not set by the server but by the client. Doing what you suggest is going
opposite to that.
This has to be done in the client (for example in the case of a multi-homing
setup, it would not work otherwise as the RM does not know the hostname/IP
visible to the user).
Also, looking at the conf is exactly what the {{ClientRMProxy}} is doing within
the {{getRMAddress()}}.
I think the current patch it is the right approach.
> 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
