You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Holden Karau (Jira)" <ji...@apache.org> on 2021/09/13 22:23:00 UTC
[jira] [Commented] (SPARK-34064) Broadcast job is not aborted even
the SQL statement canceled
[ https://issues.apache.org/jira/browse/SPARK-34064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17414621#comment-17414621 ]
Holden Karau commented on SPARK-34064:
--------------------------------------
[~inetfuture]it's hard to say since the initial fix was reverted, if you want to pick it up your self that's an option.
> Broadcast job is not aborted even the SQL statement canceled
> ------------------------------------------------------------
>
> Key: SPARK-34064
> URL: https://issues.apache.org/jira/browse/SPARK-34064
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.0.1, 3.1.1, 3.2.0
> Reporter: Lantao Jin
> Priority: Minor
> Attachments: Screen Shot 2021-01-11 at 12.03.13 PM.png
>
>
> SPARK-27036 introduced a runId for BroadcastExchangeExec to resolve the problem that a broadcast job is not aborted when broadcast timeout happens. Since the runId is a random UUID, when a SQL statement is cancelled, these broadcast sub-jobs still not canceled as a whole.
> !Screen Shot 2021-01-11 at 12.03.13 PM.png|width=100%!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org