Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-49002113
I think it makes more sense if you can't run a command than certain
commands happen to be runnable while there are no cluster resources. This sort
of execution puts more stress on the driver, as well, and things like
OutOfMemoryErrors on the driver are far more serious than on an Executor (for
example, [this
issue](https://groups.google.com/forum/#!msg/spark-users/eu9RJc3nQng/-T6wmcjMFiwJ)).
My hypothesis is that this feature is rarely useful, and often leads to
more confusion for users and potentially less stability.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
