fix(Spanner): retry logic of ExecuteStreamingSql #6149
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Potentially fixes #5880, where users are seeing
ServiceException
inExecuteStreamingSql
.Currently retry is performed till default 3 attempts, if each of these satisfy:
resumeToken
is presentServiceException
is thrownGrpc\STATUS_UNAVAILABLE
Per the fixes done in other languages Node and comment from @olavloite , it seems we should retry by below logic (point # 1 above becomes):
resumeToken
is presentTests
Added UTs which mock the ServiceExceptions with/o the resumeTokens.