GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/4660
[SPARK-4544] Properly synchronize accesses to DAGScheduler cacheLocs map
This patch addresses a race condition in DAGScheduler by properly
synchronizing accesses to its `cacheLocs` map.
This map is accessed by the `getCacheLocs` and `clearCacheLocs()` methods,
which can be called by separate threads, since DAGScheduler's
`getPreferredLocs()` method is called by SparkContext and indirectly calls
`getCacheLocs()`. If this map is cleared by the event processing thread while
another thread is computing preferred locations while submitting a job, then
this can cause the other thread to throw "NoSuchElementException: key not
found" errors.
See #3345 for additional context.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/JoshRosen/spark SPARK-4454
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/4660.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 #4660
----
commit 12d64bae25c55c7d3e02ed7e185e33f0ebd24376
Author: Josh Rosen <[email protected]>
Date: 2015-02-17T20:26:53Z
Properly synchronize accesses to DAGScheduler cacheLocs map.
----
---
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]
