Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Sprint:
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
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Benety Goh
Reporter:: Benety Goh
Participants:: Benety Goh
Votes:: 0 Vote for this issue
Watchers:: 0 Start watching this issue

Created:: Oct 14 2022 02:09:32 PM UTC
Updated:: Feb 23 2023 04:36:21 PM UTC
Resolved:: Feb 23 2023 04:30:03 PM UTC
Confidence Status Last Update:: 21/Oct/22 3:07 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates