-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Execution Team 2022-03-21, Execution Team 2022-04-04
-
67
A batch involves a single storage transaction on the primary, however it replicates as multiple oplog entries. This behaviour is generally described inĀ SERVER-55909. An additional goal for batched deletions is performance, as multiple oplog entries and timestamping introduce overhead.
Add a mechanism to emit a single oplog entry and timestamp per batch. Explore integration with the internal API for multi-document transactions.
- depends on
-
SERVER-64206 Address cyclic dependency between query_exec and transaction libraries
- Closed
- related to
-
SERVER-64506 Unify replication back-end of TransactionParticipant and WUOW
- Backlog
-
SERVER-75759 unify call to MongoDSessionCatalog in OpObserverImpl::onDelete
- Closed