Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/10993#issuecomment-179843161
@Astralidea it will deploy more than one executor on the same slave if
there are enough resources and `spark.cores.max` wasn't reached yet. It's just
that it will first spawn executors on each eligible slave in the current set of
offers, and continue iterating until one of the stop conditions is hit (not
enough resources or the `spark.cores.max` limit).
---
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]