-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Cursors
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - 2025-05-23, SE Foundations - 2025-06-06, SE Foundations - 2025-06-20
-
5
In WT-10133, we added retry logic for search, search near, next, and prev api calls if they receive a WT_ROLLBACK error.
It is OK for search and search near to retry as they are idempotent. However, it is not correct for next and prev to retry because when the btree layer returns a WT_ROLLBACK error, it resets the cursor and we will retry without the cursor positioned, which is wrong.
In WT-12431, we initially have a theory that this is the underlying root cause. But it turns out it is a separate testing issue not related. However, this doesn't mean the above scenario cannot happen and we should fix it.
- is caused by
-
WT-10133 Consider retry on rollback for more cursor API calls
-
- Closed
-
- is related to
-
WT-14570 Log a completion message for live restore
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-