[
https://issues.apache.org/jira/browse/SPARK-61218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SPARK-61218:
-----------------------------------
Labels: pull-request-available (was: )
> A session whose server-side session changed still reports is_stopped False
> and is returned by getActiveSession and getOrCreate
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-61218
> URL: https://issues.apache.org/jira/browse/SPARK-61218
> Project: Spark
> Issue Type: Bug
> Components: Connect
> Affects Versions: connect-rust-4.3.0
> Reporter: Hyukjin Kwon
> Priority: Major
> Labels: pull-request-available
> Fix For: connect-rust-4.3.0
>
>
> After a server-side session change closes the client, spark.is_stopped stays
> False, SparkSession.getActiveSession() returns the dead session, and
> getOrCreate() returns it instead of a new working session, so every call
> raises NO_ACTIVE_SESSION. stop() also still sends ReleaseSession to the
> restarted server.
> Official PySpark 4.3.0 reports is_stopped True (client.is_closed),
> getActiveSession() None, and getOrCreate() creates a new session. Official
> stop() skips ReleaseSession when the client is closed.
> The stopped flag now follows the client (SparkSession::is_stopped), and
> stop() releases only an open client.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]