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

Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2022/07/27 05:31:00 UTC

[jira] [Resolved] (SPARK-39864) ExecutionListenerManager's registration of the ExecutionListenerBus should be lazy

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

Hyukjin Kwon resolved SPARK-39864.
----------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

Issue resolved by pull request 37282
[https://github.com/apache/spark/pull/37282]

> ExecutionListenerManager's registration of the ExecutionListenerBus should be lazy
> ----------------------------------------------------------------------------------
>
>                 Key: SPARK-39864
>                 URL: https://issues.apache.org/jira/browse/SPARK-39864
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.0.0
>            Reporter: Josh Rosen
>            Assignee: Josh Rosen
>            Priority: Major
>             Fix For: 3.4.0
>
>
> Today, ExecutionListenerManager eagerly registers an ExecutionListenerBus SparkListener when it is created, even if the SparkSession has no query execution listeners registered. In applications with many short-lived SparkSessions, this can cause a buildup of empty listeners on the shared listener bus, increasing Spark listener processing times on the driver.
> If we make the registration lazy then we avoid this driver-side listener performance overhead.



--
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