Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/1525#issuecomment-50972582
If what @pwendell said is true about sparks.core.max then I think probably
need to rethink how to approach this regardless what mode we're in. I think I
gears towards safety first since this is just an optimization.
I'm still getting up to speed about the scheduling in spark, but I believe
the locality calculation is shared in TaskScheduler right?
---
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
