[
https://issues.apache.org/jira/browse/SPARK-19373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887673#comment-15887673
]
Stavros Kontopoulos commented on SPARK-19373:
---------------------------------------------
How spark leverages the node-local placement with this change?
> Mesos implementation of spark.scheduler.minRegisteredResourcesRatio looks at
> acquired cores rather than registerd cores
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-19373
> URL: https://issues.apache.org/jira/browse/SPARK-19373
> Project: Spark
> Issue Type: Bug
> Components: Mesos
> Affects Versions: 2.1.0
> Reporter: Michael Gummelt
>
> We're currently using `totalCoresAcquired` to account for registered
> resources, which is incorrect. That variable measures the number of cores
> the scheduler has accepted. We should be using `totalCoreCount` like the
> other schedulers do.
> Fixing this is important for locality, since users often want to wait for all
> executors to come up before scheduling tasks to ensure they get a node-local
> placement.
> original PR to add support: https://github.com/apache/spark/pull/8672/files
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
