Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/4051#issuecomment-71404736
@andrewor14 i think replacing maxExecutors with --num-executors is more
reasonable, because when dynamic allocation is not enable, --num-executors is
the maxExecutors. for some of running jobs, --num-executors is more large than
initialNumExecutors, so i think initialNumExecutors is better than
--num-executors.
and i agree with that we need maxExecutors to avoid that a job can get
Int.MaxValue resources.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
