-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spanner: Session not found on Read with KeySet #2718
Comments
@olavloite, would you please be able to take a look at this one? CC @hengfengli |
`Session not found` errors were not retried for read operations on a single-use read-only transaction. Fixes #2718
@olavloite thanks for quick fix. Have some more context in case you need it:
|
@ericwenn |
* fix(spanner): retry session not found for read `Session not found` errors were not retried for read operations on a single-use read-only transaction. Fixes #2718 * fix: rename method to satisfy lint check * fix: remove unused variable
Thanks for quick triage and turnaround! Looking forward to bumping our service to next release 🚀 |
* fix(spanner): retry session not found for read `Session not found` errors were not retried for read operations on a single-use read-only transaction. Fixes googleapis#2718 * fix: rename method to satisfy lint check * fix: remove unused variable
Client
Spanner (v1.7.0)
Environment
Cloud Run (fully managed)
Code
Expected behavior
Request should succeed, and the client handles maintaining the session pool.
Actual behavior
Intermittent failure, client returns:
Additional context
Re-running the same request succeeds but sometimes, very seldom, the error is returned.
There are many
Read()
calls being made by our service concurrently in the call-chain, and when the error occurs it is only for one of the calls.The text was updated successfully, but these errors were encountered: