You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (JIRA)" <ji...@apache.org> on 2019/03/15 21:59:00 UTC
[jira] [Reopened] (SPARK-27070) DefaultPartitionCoalescer can lock
up driver for hours
[ https://issues.apache.org/jira/browse/SPARK-27070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun reopened SPARK-27070:
-----------------------------------
This is reverted due to Scala-2.11 failure.
- https://github.com/apache/spark/commit/4bab69b22a50ae00b92ed6ab3b5120574dc3aa19
> DefaultPartitionCoalescer can lock up driver for hours
> ------------------------------------------------------
>
> Key: SPARK-27070
> URL: https://issues.apache.org/jira/browse/SPARK-27070
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.3.1, 2.3.2, 2.4.0
> Reporter: Yuli Fiterman
> Assignee: Yuli Fiterman
> Priority: Major
> Fix For: 3.0.0
>
>
> We're running Spark on EMR reading large datasets from S3. When trying to coalesce a UnionRDD of two large FileScanRDDs (each with a few million partitions) into around 8k partitions the driver can stall for over an hour.
>
> Profiler shows that over 90% of the time is spent in TimSort which is invoked by `pickBin`. This seems like a very inefficient way to find the least occupied PartitionGroup. IMO a better way would just using the `min` method on the ArrayBuffer of `PartitionGroup`s
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org