[SERVER-67331] Use efficient multi-deletes for range deletions Created: 16/Jun/22 Updated: 06/Dec/22 Resolved: 05/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The range-deleter is currently performing single deletes resulting in one storage transaction for each orphaned document being deleted. Purpose of this ticket is to adapt the range-deleter to use the new BatchedDeleteStage that allows deleting more documents in a single storage transaction. (Part of the code committed under |
| Comments |
| Comment by Pierlauro Sciarelli [ 05/Jul/22 ] |
|
Closing as duplicate of |