[SERVER-44160] Make cleanupOrphaned just wait for all range deletion tasks on the ns to finish in FCV 4.4 when 'disableResumableRangeDeleter' is false Created: 22/Oct/19 Updated: 29/Oct/23 Resolved: 19/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Sprint: | Sharding 2020-02-24, Sharding 2020-03-09, Sharding 2020-03-23 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Linked BF Score: | 24 | ||||||||||||
| Description |
|
After the resumable range deleter project is finished, there should never be orphaned ranges that are not tracked by config.rangeDeletions and submitted to the range deleter when ready, so cleanupOrphaned should be able to just wait for the scheduled deletion to complete rather than submitting a new range for deletion. |
| Comments |
| Comment by Githook User [ 30/Mar/20 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: (cherry picked from commit 5ab0e5571a01dea57897fa77f1419f415f4f15b4) |
| Comment by Githook User [ 18/Mar/20 ] |
|
Author: {'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |