You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding intents batch we don't hold RequestScope object, that could cause situation when transaction metadata is deleted, but intents for this transaction still exists.
The text was updated successfully, but these errors were encountered:
…ords
Summary:
RequestScope is an utility class that allows us to prevent deletion of transaction metadata while it is still being used by a request. When adding a batch of provisional records, we currently don't hold a RequestScope object. This could cause a situation when transaction metadata is deleted, but provisional records for this transaction remain.
In this diff we are extending the lifetime of the RequestScope to fix this issue.
Also added handling of this case while getting transaction status for existing provisional records.
Test Plan: Jenkins
Reviewers: timur, robert, mikhail
Reviewed By: mikhail
Subscribers: ybase
Differential Revision: https://phabricator.dev.yugabyte.com/D5729
kmuthukk
changed the title
Intents could be present w/o transaction metadata
[dist-txns] Intents could be present w/o transaction metadata
Nov 15, 2018
When adding intents batch we don't hold RequestScope object, that could cause situation when transaction metadata is deleted, but intents for this transaction still exists.
The text was updated successfully, but these errors were encountered: