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] [Commented] (YARN-549) Asynchronous application submission
Date Fri, 19 Apr 2013 22:45:17 GMT

    [ https://issues.apache.org/jira/browse/YARN-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636972#comment-13636972

Zhijie Shen commented on YARN-549:

Does it make sense to print some log every so often to let users now, if the application is
stuck in new/saving state for a long time? Say every 10-15 times of the polling-interval ?
YarnClient.getApplicationReport has opened the door for querying application states.If the
client is blocked by YarnClient.submitApplication for a long time, I think the client can
use YarnClient.getApplicationReport to query the state. Then, it can decide whether it want
to terminate the submission or something. IMHO, it's the client's business.
> 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