Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/9752#discussion_r45224067
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -422,6 +422,37 @@ private[spark] class MesosClusterScheduler(
desc.schedulerProperties.get("spark.cores.max").map { v =>
options ++= Seq("--total-executor-cores", v)
}
+
+ /**
+ * The properties to pass along from Spark Submit to the Mesos
Scheduler.
+ *
http://spark.apache.org/docs/1.5.1/configuration.html#available-properties
+ */
+ val propertiesToPropagate = Set(
+ "spark.driver.extraClassPath",
--- End diff --
I agree with @tnachen that it's probably better to include all of them, and
blacklist the ones that don't make sense. Either way it's a bit of a
maintenance burden whenever a new property gets added, but it's more likely
that we'd need it to be passed down than not.
---
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]
