GitHub user xuanyuanking opened a pull request:
https://github.com/apache/spark/pull/16135
SPARK-18700: add ReadWriteLock for each table's relation in cache
## What changes were proposed in this pull request?
As the scenario describe in
[SPARK-18700][https://issues.apache.org/jira/browse/SPARK-18700], when
cachedDataSourceTables invalided, the coming few queries will fetch all
FileStatus in listLeafFiles function. In the condition of table has many
partitions, these jobs will occupy much memory of driver finally may cause
driver OOM.
In this patch, add ReadWriteLock for each table's relation in cache not for
the whole cachedDataSourceTables, keep a hashMap which key is TableIdentifier
and value is relevant ReadWriteLock.
## How was this patch tested?
The existing tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xuanyuanking/spark SPARK-18700
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/16135.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 #16135
----
commit 8718ec31d1234c04755467c872c5a9ab0991fa95
Author: xuanyuanking <xyliyuanj...@gmail.com>
Date: 2016-12-04T06:41:14Z
SPARK-18700: add ReadWriteLock for each table's relation in cache
----
---
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
