[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533465#comment-17533465
]
Jacek Laskowski commented on SPARK-17556:
-----------------------------------------
Given:
# "I'm running a large query with over 100,000 tasks."
# "Total size of serialized results ... is bigger than
spark.driver.maxResultSize".
I think the issue is no a broadcast join but the size of the result (as
computed by these 100k tasks). They have to report back to the driver and I
can't think of a reason why a broadcast join would make it any worse? I must be
missing something obvious (and chimed in to learn a bit about Spark SQL from
you today :))
> Executor side broadcast for broadcast joins
> -------------------------------------------
>
> Key: SPARK-17556
> URL: https://issues.apache.org/jira/browse/SPARK-17556
> Project: Spark
> Issue Type: New Feature
> Components: Spark Core, SQL
> Reporter: Reynold Xin
> Priority: Major
> Attachments: executor broadcast.pdf, executor-side-broadcast.pdf
>
>
> Currently in Spark SQL, in order to perform a broadcast join, the driver must
> collect the result of an RDD and then broadcast it. This introduces some
> extra latency. It might be possible to broadcast directly from executors.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
