24-3: Abort volatile transactions during graceful restarts #12808
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.
Changelog entry
Abort volatile transactions during graceful restarts.
Changelog category
Additional information
Volatile transactions don't migrate across restarting datashards (yet), and effectively abort when any shard restarts. However, since KQP doesn't receive any reply it cannot be sure of the outcome, and replied with an
UNDETERMINEDerror since transaction could have committed, restarting just before it would have tried sending the reply. This change short circuits volatile transaction causing a deterministic abort, instead of a likely futile attempt at execution.Fixes #12303.