hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-549) Asynchronous application submission
Date Fri, 19 Apr 2013 07:13:16 GMT

     [ https://issues.apache.org/jira/browse/YARN-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Zhijie Shen updated YARN-549:

    Attachment: YARN-549.1.patch

I drafted a patch, which implemented what had been described in the last comment. One difference
is that RMAppManager#submitApplcation is not synchronized because concurrent application submissions
are allowed to enter the function (see TestClientRMService#testConcurrentAppSubmit). Logically,
concurrent app submissions with different appId will not influence each other, while only
one app submission will be admitted among those with the same appId.

In addition, YarnClientImpl#submitApplication is modified to delay returning applicationId
until the  submitted application has enter SUBMITTED or later states.
> 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

View raw message