[SERVER-63047] Make delete batches fully transactional Created: 27/Jan/22 Updated: 29/Oct/23 Resolved: 25/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Josef Ahmad | Assignee: | Josef Ahmad |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2227-M2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Execution Team 2022-03-21, Execution Team 2022-04-04 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 67 | ||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 24/Mar/22 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: |
| Comment by Githook User [ 24/Mar/22 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: |
| Comment by Josef Ahmad [ 04/Mar/22 ] |
|
I've split the first task from the list above into |
| Comment by Josef Ahmad [ 04/Mar/22 ] |
|
Summary of the main tasks needed to use the internal multi-document transaction API for batching deletes.
|