-
Notifications
You must be signed in to change notification settings - Fork 28.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[SPARK-48056][CONNECT][PYTHON] Re-execute plan if a SESSION_NOT_FOUND…
… error is raised and no partial response was received ### What changes were proposed in this pull request? Similar to OPERATION_NOT_FOUND, re-attempt to execute the original spark connect plan when a SESSION_NOT_FOUND is received from the spark connect service and no partial responses were previously received. ### Why are the changes needed? This error has been noticed to occur during a cluster cold start and when a request arrives when the connect service is not fully initialized. ### Does this PR introduce _any_ user-facing change? Prevoiusly, connect-based pyspark APIs would fail with the error code "INVALID_HANDLE.SESSION_NOT_FOUND" in the very first request to the service. With this change, the client will now automatically retry. ### How was this patch tested? Attached unit tests. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #46297 from nija-at/session-not-found. Authored-by: Niranjan Jayakar <[email protected]> Signed-off-by: Hyukjin Kwon <[email protected]>
- Loading branch information
1 parent
ae5da18
commit 2f31d05
Showing
2 changed files
with
85 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters