-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
With SERVER-39680, we'll compute the oldest active transaction timestamp by reading the transaction table. For prepared transactions, prevOpTime happens to be the first optime of the transaction in the old applyOps format. With the new format of both unprepared and prepared transactions, we need to add a new field in the transaction table to track the first timestamp of any oplog entry in a transaction.
- duplicates
-
SERVER-39680 Maintain the oldest active transaction timestamp only with the transaction table
- Closed
- related to
-
SERVER-39829 Consider in-progress transactions when calculating the oldest active transaction timestamp
- Closed