[SERVER-70898] replicate batched operations comprising of single inserts as ‘i’ insert operations rather than applyOps entries Created: 27/Oct/22 Updated: 26/Apr/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Sprint: | Execution Team 2022-11-14, Execution Team 2022-11-28 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We anticipate using the BatchedWriteContext class to replicate groups of inserts for internal operations, such as renameCollection. Currently, batched operations are unconditionally replicated as applyOps oplog entries. For singleton batched operations, it would be ideal to replicate as the underlying CRUD operation type, in this case as a single ‘i’ insert CRUD operation. Since there is no user-facing command that would generate a batch of inserts, this would be a good opportunity to introduce a C++ unit test to exercise some of the BatchedWriteContext functionality for handling single and multiple inserts. |
| Comments |
| Comment by Benety Goh [ 27/Oct/22 ] |
|
This is a follow-up to |