Github user klueska commented on the issue:
https://github.com/apache/spark/pull/17235
Can you give a bit more context on what this new parameter is supposed to
enforce? Maybe it's just the same of the parameter that's confusing me.
---
If your project is set up for it, you can
Github user klueska commented on a diff in the pull request:
https://github.com/apache/spark/pull/14644#discussion_r78298850
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosCoarseGrainedSchedulerBackend.scala
---
@@ -103,6 +103,7 @@ private[spark
Github user klueska commented on a diff in the pull request:
https://github.com/apache/spark/pull/14644#discussion_r78297397
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosCoarseGrainedSchedulerBackend.scala
---
@@ -103,6 +103,7 @@ private[spark
Github user klueska commented on a diff in the pull request:
https://github.com/apache/spark/pull/14644#discussion_r78012264
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosCoarseGrainedSchedulerBackend.scala
---
@@ -103,6 +103,7 @@ private[spark
Github user klueska commented on the issue:
https://github.com/apache/spark/pull/14644
I just tested this against the newest GPU support in Mesos 1.0.1 and
everything seems to work as expected. My only question is the use of
`spark.mesos.gpus.max` instead
Github user klueska commented on a diff in the pull request:
https://github.com/apache/spark/pull/14644#discussion_r77965263
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosCoarseGrainedSchedulerBackend.scala
---
@@ -103,6 +103,7 @@ private[spark
