Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/5297#issuecomment-89397079
I prefer the current way (not waiting for running). The YarnClient we are
using makes sure it gets submitted before returning. Beyond that we shouldn't
really have to wait for it to actually run. If your cluster is busy that could
be an indefinite amount of time. In many cases I just want to start an
application and I don't really care if it actually starts running immediately
or in 10 minutes. The first application report is useful if it fails. For
instance I submit to a queue that doesn't exist or have some bad config.
Not that this matters to much, but MapReduce also has a submit and no wait
option and it doesn't wait for running, just submitted. I only mention it
because if people are coming from that they might have expectations on the
behavior.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
