yi.wu 0ad382747d [SPARK-36782][CORE][FOLLOW-UP] Only handle shuffle block in separate thread pool ... ### What changes were proposed in this pull request? This's a follow-up of https://github.com/apache/spark/pull/34043. This PR proposes to only handle shuffle blocks in the separate thread pool and leave other blocks the same behavior as it is. ### Why are the changes needed? To avoid any potential overhead. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass existing tests. Closes #34076 from Ngone51/spark-36782-follow-up. Authored-by: yi.wu <yi.wu@databricks.com> Signed-off-by: Gengliang Wang <gengliang@apache.org> (cherry picked from commit 9d8ac7c8e9) Signed-off-by: Gengliang Wang <gengliang@apache.org>		2021-09-23 16:30:25 +08:00
..
benchmarks	[SPARK-32210][CORE] Fix NegativeArraySizeException in MapOutputTracker with large spark.default.parallelism	2021-08-16 09:11:51 -07:00
src	[SPARK-36782][CORE][FOLLOW-UP] Only handle shuffle block in separate thread pool	2021-09-23 16:30:25 +08:00
pom.xml	Preparing development version 3.2.1-SNAPSHOT	2021-09-18 11:30:12 +00:00