[
https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913857#comment-13913857
]
Xuan Gong commented on YARN-1410:
---------------------------------
bq. can we do this in the RM?
Done
bq. Please put some comments in the test to help understand what is being
tested. e.g. testing that failed over RM accepts the appId in submitContext
even though it does not exist internally
added
bq. If the test is doing failover in the test method then why is
submitApplication(ApplicationId oldAppId) also causing failover?
removed
bq. Looks like the RM already blindly accepts the appId present in the
submitContext.
Yes.
bq. Please change the title of the jira and link it to the other 2 jiras.
Done
> Handle RM fails over after getApplicationID() and before submitApplication().
> -----------------------------------------------------------------------------
>
> 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, YARN-1410.7.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)
