Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/4051#issuecomment-70295188
To distill the motivation on the JIRA and make sure we're on the same page:
in most situations (including Hive-on-Spark), users don't or can't know how
many resources their app will be able to take advantage of, so they want the
max to be effectively unbounded. Requesting all these resources on startup
wouldn't make sense.
If the concern is that there will be application startup delay, maybe it
would make sense to add an initialExecutors property?
I think in most situations
---
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]
