-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: Needs Triage
-
Component/s: Replication
-
None
-
Replication
Currently, we only write down oplog entries for in progress transactions if they are prepared. We have a few invariants in transaction_participant.cpp that make sure we do not set the oldest oplog entry timestamp if the transaction is not prepared.
This behavior changes once we allow multiple oplog entries per transaction, so we should remove those invariants for PM-1035.
- duplicates
-
SERVER-40018 Remove ServerTransactionsMetrics::getOldestActiveOpTime
- Closed