You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2026/01/20 03:35:00 UTC

[jira] [Resolved] (SPARK-55016) Prevent stack overflow when SQLConf.get is called during sessionState initialization

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

Wenchen Fan resolved SPARK-55016.
---------------------------------
    Fix Version/s: 4.2.0
       Resolution: Fixed

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

> Prevent stack overflow when SQLConf.get is called during sessionState initialization
> ------------------------------------------------------------------------------------
>
>                 Key: SPARK-55016
>                 URL: https://issues.apache.org/jira/browse/SPARK-55016
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 4.0.1, 3.5.7, 4.1.1
>            Reporter: L. C. Hsieh
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.2.0
>
>
> There is a potential stack overflow issue that can occur when SQLConf.get.getConf() is called during SparkSession's sessionState initialization. The problem happens when:
>     SparkSession becomes active via setDefaultAndActiveSession
>     sessionState lazy val starts initializing (not yet complete)
>     During initialization, code calls SQLConf.get.getConf()
>     confGetter tries to access sessionState.conf
>     This creates a recursive loop because sessionState is still initializing



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