GitHub user ash211 opened a pull request:
https://github.com/apache/spark/pull/2519
SPARK-3526 Add section about data locality to the tuning guide
cc @kayousterhout
I have a few outstanding questions from compiling this documentation:
- What's the difference between NO_PREF and ANY? I understand the
implications of the ordering but don't know what an example of each would be
- Why is NO_PREF ahead of RACK_LOCAL? I would think it'd be better to
schedule rack-local tasks ahead of no preference if you could only do one or
the other. Is the idea to wait longer and hope for the rack-local tasks to
turn into node-local or better?
- Will there be a datacenter-local locality level in the future? Apache
Cassandra for example has this level
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ash211/spark SPARK-3526
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/2519.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2519
----
commit 20e0e31158fe0350b8f59617f2228a48c34274ef
Author: Andrew Ash <[email protected]>
Date: 2014-09-24T08:50:07Z
SPARK-3526 Add section about data locality to the tuning guide
----
---
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]
