You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/09/03 04:02:00 UTC

[jira] [Updated] (SPARK-53446) Improve broadcast block cleanup performance in BlockManager to prevent memory pressure and OOM

     [ https://issues.apache.org/jira/browse/SPARK-53446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated SPARK-53446:
-----------------------------------
    Labels: pull-request-available  (was: )

> Improve broadcast block cleanup performance in BlockManager to prevent memory pressure and OOM
> ----------------------------------------------------------------------------------------------
>
>                 Key: SPARK-53446
>                 URL: https://issues.apache.org/jira/browse/SPARK-53446
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 3.4.3, 3.4.4
>            Reporter: JacobZheng
>            Priority: Major
>              Labels: pull-request-available
>
> When Spark applications continuously generate a large number of broadcast tasks, the BlockInfoManager’s blockInfoWrappers keeps accumulating broadcast block metadata. As a result, the BlockManager.removeBroadcast method becomes increasingly slower over time because it needs to iterate through a growing number of entries.
> This performance degradation can lead to severe memory pressure and eventually trigger an OOM error in long-running jobs with frequent broadcasts.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org