[
https://issues.apache.org/jira/browse/YARN-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637009#comment-13637009
]
Zhijie Shen commented on YARN-549:
----------------------------------
{quote}
Any reason why you are moving some of that code into RMAppManager?
{quote}
Before the patch, part of sanity check is done in
ClientRMService#submitApplication and part in RMAppManager#submitApplication,
and applicationId is checked twice in both sides. I'm fine with either merging
ClientRMService#submitApplication into RMAppManager#submitApplication or vice
versa, but it is good to put the similar sanity checks at the same place. So,
let me move code to ClientRMService to make RMAppManager thin.
> Asynchronous application submission
> -----------------------------------
>
> Key: YARN-549
> URL: https://issues.apache.org/jira/browse/YARN-549
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Attachments: Proposal of Asynchronous Application Submission_v1.pdf,
> YARN-549.1.patch
>
>
> Currently, when submitting an application, storeApplication will be called
> for recovery. However, it is a blocking API, and is likely to block
> concurrent application submissions. Therefore, it is good to make application
> submission asynchronous, and postpone storeApplication.
--
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
