Github user gpang commented on a diff in the pull request:
https://github.com/apache/spark/pull/18098#discussion_r118590493
--- Diff:
resource-managers/mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosCoarseGrainedSchedulerBackend.scala
---
@@ -502,6 +521,25 @@ private[spark] class
MesosCoarseGrainedSchedulerBackend(
)
}
+ private def satisfiesLocality(offerHostname: String): Boolean = {
+ if (hostToLocalTaskCount.nonEmpty) {
--- End diff --
I see what you mean. I wanted these semantics to only be in-effect if
location information is available. If there is no location information, I don't
think there is a reason to wait for a delay.
So, the original semantics I wanted was, "If location information is
available, launch an executor on a host only when we have a task that wants to
be on that host, or the configurable delay has elapsed."
What should the semantics be?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
