Description
Currently in coarse grained mesos mode, it's expected that we only launch one Mesos executor that launches one JVM process to launch multiple spark executors.
However, this become a problem when the JVM process launched is larger than an ideal size (30gb is recommended value from databricks), which causes GC problems reported on the mailing list.
We should support launching mulitple executors when large enough resources are available for spark to use, and these resources are still under the configured limit.
This is also applicable when users want to specifiy number of executors to be launched on each node
Attachments
Issue Links
- is related to
-
SPARK-12248 Make Spark Coarse Mesos Scheduler obey limits on memory/cpu ratios
- Resolved
- links to