[SERVER-72298] Use batch deletions to delete orphaned ranges Created: 21/Dec/22 Updated: 10/Jan/23 Resolved: 10/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||
| Participants: | |||||||||||||
| Story Points: | 3 | ||||||||||||
| Description |
|
PM-2227 introduced a new API to efficiently remove documents using batching. Currently the range deleter is not very efficient because it still deletes document one by one, executing every single deletion in its own WriteUnitOfWork. The goal of this ticket is to make the range deleter more efficient by using the new batch deletion API. |