[
https://issues.apache.org/jira/browse/SPARK-46660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon resolved SPARK-46660.
----------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 44670
[https://github.com/apache/spark/pull/44670]
> ReattachExecute requests do not refresh aliveness of SessionHolder
> ------------------------------------------------------------------
>
> Key: SPARK-46660
> URL: https://issues.apache.org/jira/browse/SPARK-46660
> Project: Spark
> Issue Type: Bug
> Components: Connect
> Affects Versions: 4.0.0
> Reporter: Venkata Sai Akhil Gudesa
> Assignee: Venkata Sai Akhil Gudesa
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> In the first executePlan request, creating the {{ExecuteHolder}} triggers
> {{getOrCreateIsolatedSession}} which refreshes the aliveness of
> {{{}SessionHolder{}}}. However in {{ReattachExecute}} , we fetch the
> {{ExecuteHolder}} directly without going through the {{SessionHolder}} (and
> hence making it seem like the {{SessionHolder}} is idle).
>
> This would result in long-running queries (which do not send release execute
> requests since that refreshes aliveness) failing because the
> {{SessionHolder}} would expire during active query execution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
