[SERVER-70572] support applyOps oplog entry chaining for BatchedWriteContext Created: 14/Oct/22 Updated: 23/Feb/23 Resolved: 23/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| 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 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
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. |