[
https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912071#comment-13912071
]
Xuan Gong commented on YARN-1410:
---------------------------------
Create https://issues.apache.org/jira/browse/YARN-1763 to track 2) RM fail
overs *during* the submitApplication call.
Create https://issues.apache.org/jira/browse/YARN-1764 to track 3) RM fails
over *after* the submitApplication call and before the subsequent
getApplicationReport().
This ticket is used to track 1) RM fails over after getApplicationID() and
*before* submitApplication().
Create a patch which includes :
* make RM accept the applicationId in the context. Nothing need to be changed
here.
* If there is no applicationId specified in the context, RM will assign a new
ApplicationId.
Also added two testcases to test AppSubmissionWithApplicationId and
AppSubmissionWithoutApplicationId
> Handle client failover during 2 step client API's like app submission
> ---------------------------------------------------------------------
>
> Key: YARN-1410
> URL: https://issues.apache.org/jira/browse/YARN-1410
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Xuan Gong
> Attachments: YARN-1410-outline.patch, YARN-1410.1.patch,
> YARN-1410.2.patch, YARN-1410.2.patch, YARN-1410.3.patch, YARN-1410.4.patch,
> YARN-1410.5.patch, YARN-1410.6.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> App submission involves
> 1) creating appId
> 2) using that appId to submit an ApplicationSubmissionContext to the user.
> The client may have obtained an appId from an RM, the RM may have failed
> over, and the client may submit the app to the new RM.
> Since the new RM has a different notion of cluster timestamp (used to create
> app id) the new RM may reject the app submission resulting in unexpected
> failure on the client side.
> The same may happen for other 2 step client API operations.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
