[
https://issues.apache.org/jira/browse/YARN-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13711392#comment-13711392
]
Vinod Kumar Vavilapalli commented on YARN-918:
----------------------------------------------
This patch can go in only after YARN-701, you can apply it after applying the
latest patch there.
bq. Not having the ApplicationAttemptId in the payload, would affect in any way
unmanaged AMs?
Unmanaged AM is broken after YARN-701 itself, as I mentioned
[here|https://issues.apache.org/jira/browse/YARN-701?focusedCommentId=13703933&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13703933].
But once the main issue with Unmanaged AMs is fixed, i.e. sending a token
across and passing it down to the real AM, this JIRA won't have any impact on
unmanaged AMs.
> ApplicationMasterProtocol doesn't need ApplicationAttemptId in the payload
> after YARN-701
> -----------------------------------------------------------------------------------------
>
> Key: YARN-918
> URL: https://issues.apache.org/jira/browse/YARN-918
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Priority: Blocker
> Attachments: YARN-918-20130715.txt, YARN-918-20130717.txt
>
>
> Once we use AMRMToken irrespective of kerberos after YARN-701, we don't need
> ApplicationAttemptId in the RPC pay load. This is an API change, so doing it
> as a blocker for 2.1.0-beta.
--
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
