-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Execution Team 2022-12-12, Execution Team 2023-02-20, Execution Team 2022-12-26, Execution Team 2023-01-09, Execution Team 2023-02-06, Execution Team 2023-03-06
A WriteUnitOfWork with batched writes enabled may emit at most one applyOps oplog entry currently. We would like to re-examine this limitation and look at reusing some of the formatting changes we did for large multi-doc transactions, which emits a chain of applyOps oplog entries to be interpreted as one logical unit for secondary oplog application.
- duplicates
-
SERVER-70903 support multi-oplog format for batched operations
- Closed
-
SERVER-70905 handle multi-oplog batched writes during oplog application
- Closed
- related to
-
SERVER-70765 add configurable batch limits for multi-oplog batched writes
- Closed
-
SERVER-70899 move logOplogEntries() from OpObserverImpl to TransactionOperations
- Closed
-
SERVER-70903 support multi-oplog format for batched operations
- Closed