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 "Omkar Vinit Joshi (JIRA)" <ji...@apache.org> on 2013/07/16 23:18:48 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13710262#comment-13710262 ] 

Omkar Vinit Joshi commented on YARN-918:
----------------------------------------

Thanks vinod...took a look at the patch....pretty straight forward.. +1

                
> 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