Skip to content
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

BeginTransaction shouldn't retry indefinitely on FAILED_PRECONDITION #177

Closed
skuruppu opened this issue Apr 23, 2020 · 0 comments · Fixed by #181
Closed

BeginTransaction shouldn't retry indefinitely on FAILED_PRECONDITION #177

skuruppu opened this issue Apr 23, 2020 · 0 comments · Fixed by #181
Assignees
Labels
api: spanner priority: p1 type: bug

Comments

@skuruppu
Copy link
Contributor

@skuruppu skuruppu commented Apr 23, 2020

A team reported that they're seeing BeginTransaction retrying indefinitely on FAILED_PRECONDITION errors.

This is an issue similar to #16. For now, just giving up on the retries for this specific error would do.

But perhaps we can consider not retrying for all non-retryable errors as well in a separate PR?

@skuruppu skuruppu added type: bug priority: p1 api: spanner labels Apr 23, 2020
olavloite added a commit that referenced this issue Apr 25, 2020
Most errors that occur during preparing a session for a read/write
transaction should be considered permanent, and should stop the
automatic preparing of sessions. Any subsequent call to get a read/write
session will cause an in-process BeginTransaction RPC to be executed. If
the problem has been fixed in the meantime, the RPC will succeed and the
automatic prepare of sessions will start again. Otherwise, the error is
propagated to the user.

Fixes #177
olavloite added a commit that referenced this issue Apr 26, 2020
Most errors that occur during preparing a session for a read/write
transaction should be considered permanent, and should stop the
automatic preparing of sessions. Any subsequent call to get a read/write
session will cause an in-process BeginTransaction RPC to be executed. If
the problem has been fixed in the meantime, the RPC will succeed and the
automatic prepare of sessions will start again. Otherwise, the error is
propagated to the user.

Fixes #177
olavloite added a commit that referenced this issue Apr 28, 2020
Most errors that occur during preparing a session for a read/write transaction should be considered permanent, and should stop the automatic preparing of sessions. Any subsequent call to get a read/write session will cause an in-process BeginTransaction RPC to be executed. If
the problem has been fixed in the meantime, the RPC will succeed and the automatic prepare of sessions will start again. Otherwise, the error is propagated to the user.

Fixes #177
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner priority: p1 type: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants