-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 5.3 Required
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
-
(copied to CRM)
-
19
The commit_prepared_transaction_errors.js test is reproducing the situation when a prepared transaction fails because it has no commitTimestamp and then is aborted with `abortTransaction_forTesting()`. The next transaction started for the same data entry fails in WiredTigerIdIndex::_insert with:
"WiredTigerIdIndex::_insert: index: _id_; uri: table:index-161--1657325371758770379 :: caused by :: WriteConflict
I verified that the conflict happens in the C-level code `__wt_cursor int __F(insert)(WT_CURSOR *cursor)`. I verified that the `WiredTigerItem keyItem` passed to both transactions is identical, so almost certainly it means the previous index key was not removed from WT table when the transaction abort already returned.
- depends on
-
WT-8753 Add tombstone when rolling back in-memory, prepared, reconciled updates
- Closed