[SPARK-46660] ReattachExecute requests do not refresh aliveness of SessionHolder

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.0
• Fix Version/s: 4.0.0
• Component/s: Connect
• Labels: pull-request-available
• Assignee: Venkata Sai Akhil Gudesa
• Reporter: Venkata Sai Akhil Gudesa
• Created: 10/Jan/24 20:04
• Updated: 15/Jan/24 08:35
• Resolved: 15/Jan/24 08:35

Description

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.

Issue Links

• links to: GitHub Pull Request #44670