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
IntentAwareIterator can miss intents due to IntentAwareIterator::SetIntentUpperbound optimization. This can happen in case when we have a mix of regular records and intents and reading at the time before regular record was written, but after intent transaction was committed, for example:
The reason is the due to incorrect setting of intent upper bound based regular record with ht>read_time, iterator skips intents which are later than this record, but were committed before read_time.
The text was updated successfully, but these errors were encountered:
…forward scan
Summary:
IntentAwareIterator can miss intents in case when we have a mix of regular records and
intents and reading at the time before regular record was written, but after intent transaction was
committed. The reason is the due to incorrect setting of intent upper bound based regular record with ht>read_time, iterator skips intents which are later than this record, but were committed before read_time.
The fix is to do lazy setting of upper bound for intents and lazy scanning for intents inside
valid() function. Also added tests to catch issue which was fixed.
Test Plan: Jenkins
Reviewers: mikhail, robert, sergei
Reviewed By: sergei
Subscribers: ybase
Differential Revision: https://phabricator.dev.yugabyte.com/D5344
IntentAwareIterator
can miss intents due toIntentAwareIterator::SetIntentUpperbound
optimization. This can happen in case when we have a mix of regular records and intents and reading at the time before regular record was written, but after intent transaction was committed, for example:The reason is the due to incorrect setting of intent upper bound based regular record with ht>read_time, iterator skips intents which are later than this record, but were committed before read_time.
The text was updated successfully, but these errors were encountered: