[
https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859199#comment-13859199
]
Karthik Kambatla commented on YARN-1410:
----------------------------------------
Like the idea of calling createApplication() from within submitApplication() if
the appId is not set in ASC. There should also be a version of
ASC.newInstance() that doesn't require an applicationId and can be used by the
clients.
Another bizarre alternative would be to prematurely write the appId to the
state-store on createApplication() even before an application is submitted. So,
there could be appIds in the store that don't correspond to any applications -
which is kind of weird and can lead to the store bloating up and other
undesirable side-effects.
> 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.1.patch
>
>
> 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)
