GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/18073
[SPARK-20848][SQL] Shutdown the pool after reading parquet files
## What changes were proposed in this pull request?
From JIRA: On each call to spark.read.parquet, a new ForkJoinPool is
created. One of the threads in the pool is kept in the WAITING state, and never
stopped, which leads to unbounded growth in number of threads.
We should shutdown the pool after reading parquet files.
## How was this patch tested?
Added a test to ParquetFileFormatSuite.
Please review http://spark.apache.org/contributing.html before opening a
pull request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/viirya/spark-1 SPARK-20848
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/18073.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 #18073
----
commit e4940b9e511a314144db042dfaa6b0f2f4a4a45d
Author: Liang-Chi Hsieh <vii...@gmail.com>
Date: 2017-05-23T12:54:21Z
Shutdown the pool after reading parquet files.
----
---
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
