Hanging indefinitely #2494
Assignees
Labels
api: spanner
Issues related to the googleapis/java-spanner API.
Comments
product-auto-label
bot
added
the
api: spanner
|
Hi @Sourc, thanks for logging the issue! Do you mean v6.42.1 (and not 6.24.1 in your initial description)? Support case mentions v6.42.1. |
|
Hi, yes a typo. I've corrected it now👍 |
olavloite
added a commit
that referenced
this issue
Jul 25, 2023
Use the streamWaitTimeout that has been set on the call context when polling from the gRPC stream. This prevents the stream from blocking forever if for some reason the stream is no longer delivering data, and also no error is propagated to the client. The default stream wait timeout that is set for all call contexts is 30 mins. This value can be overridden by configuring a custom call context for a specific query. Fixes #2494
olavloite
added a commit
that referenced
this issue
Jul 31, 2023
* fix: apply stream wait timeout Use the streamWaitTimeout that has been set on the call context when polling from the gRPC stream. This prevents the stream from blocking forever if for some reason the stream is no longer delivering data, and also no error is propagated to the client. The default stream wait timeout that is set for all call contexts is 30 mins. This value can be overridden by configuring a custom call context for a specific query. Fixes #2494 * test: add a wait time to the mock server to ensure that a timeout occurs * chore: add clirr ignore * docs: add test + comment for zero timeout * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md --------- Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, this issue is related to the support case 45040288.
A short while ago we had multiple of our services that use Spanner, both with the latest Spanner version at the time (6.42.1) but some using slightly older ones as well, hang indefinitely on this particular row. The only solution when that happened was to restart the service, which would fix the issue - even though it often happened again after a while.
This happened quite often during a two week period towards at least one particular Spanner instance, and we haven't seen it since a couple of weeks now. We have also not been able to determine the exact conditions under which this issue presents itself - We do not believe it to be a recent code change, as we saw it on some services that haven't been updated for months. The code that froze was just a regular
resultSet.next()call, preceeded by asingleUse().read(...), with appropriate closing etc.Since we don't have a reliable way to reproduce this issue, I believe the most straightforward way to solve it would be to implement a timeout mechanic like mentioned in the TODO-comment in the code already.
The text was updated successfully, but these errors were encountered: