-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Transactions
-
SE Transactions - 2026-03-13, SE Transactions - 2026-03-27
-
8
When a standby steps up, it needs to copy the content from the stable table to the ingest table. If a key has been prepared (either committed or rolled back now) and the prepared timestamp is stable but the durable timestamp or rollback timestamp is not stable, we must have written a prepared update to the stable table. In this case, during the draining process, we need to resolve this prepared update on the stable table. Otherwise, we will have a prepared update never resolved on the stable table.
This ticket aims to implement this logic based on the work done in WT-16743.
- is related to
-
WT-16743 Refactor txn prepare resolution code to not depend on any session specific data
-
- Closed
-