[
https://issues.apache.org/jira/browse/YARN-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637101#comment-13637101
]
Vinod Kumar Vavilapalli commented on YARN-549:
----------------------------------------------
bq. 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 ?
CLI is the most common user of YarnClient. Having a log there is helpful for
command line clients. Think command line clients which submit jobs like when
you do "hadoop jar".
Again, we don't need to add it for every polling iteration. Only if submission
is stuck for say 10 times polling interval - that way it will not be printed at
all in the common case, but will print something that is really useful when
submission is stuck for some reason.
> 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
