You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2013/07/16 01:08:48 UTC
[jira] [Updated] (YARN-918) ApplicationMasterProtocol doesn't need
ApplicationAttemptId in the payload after YARN-701
[ https://issues.apache.org/jira/browse/YARN-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated YARN-918:
-----------------------------------------
Attachment: YARN-918-20130715.txt
Here's a patch that works. Needs to be applied on top of YARN-701. It simply removes the ApplicationAttemptId from the protocol request objects.
> 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
>
>
> 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