hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-918) ApplicationMasterProtocol doesn't need ApplicationAttemptId in the payload after YARN-701
Date Wed, 17 Jul 2013 18:11:48 GMT

     [ 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-20130717.txt

Updated patch to be applied on top of latest patch at YARN-701.
                
> 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

Mime
View raw message