Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/4027#discussion_r25097455
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/CoarseMesosSchedulerBackend.scala
---
@@ -63,20 +63,25 @@ private[spark] class CoarseMesosSchedulerBackend(
// Maximum number of cores to acquire (TODO: we'll need more flexible
controls here)
val maxCores = conf.get("spark.cores.max", Int.MaxValue.toString).toInt
+ val maxExecutorsPerSlave =
conf.getInt("spark.mesos.coarse.executors.max", 1)
+ val maxCpusPerExecutor = conf.getInt("spark.mesos.coarse.cores.max",
Int.MaxValue)
+
// Cores we have acquired with each Mesos task ID
val coresByTaskId = new HashMap[Int, Int]
var totalCoresAcquired = 0
- val slaveIdsWithExecutors = new HashSet[String]
+ // Contains a mapping of slave ids to the number of executors launched.
+ val slaveIdsWithExecutors = new HashMap[String, Int]
val taskIdToSlaveId = new HashMap[Int, String]
val failuresBySlaveId = new HashMap[String, Int] // How many times tasks
on each slave failed
-
val extraCoresPerSlave = conf.getInt("spark.mesos.extra.cores", 0)
var nextMesosTaskId = 0
+ val memRequired: Double = MemoryUtils.calculateTotalMemory(sc)
--- End diff --
what does `memRequired` mean? Did you mean `memoryPerExecutor`?
---
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]