[SERVER-63243] Range deleter must not clean up orphan ranges in a round-robin fashion Created: 03/Feb/22 Updated: 29/Oct/23 Resolved: 07/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.10, 4.4.16, 6.0.0-rc10, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v6.0, v5.0, v4.4
|
||||
| Sprint: | Sharding EMEA 2022-04-04, Sharding EMEA 2022-06-13 | ||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
In presence of more than one ready range deletion referring ranges containing more than rangeDeleterBatchSize documents, the range-deleter is currently working in a round-robin fashion. Example with ready range deletions task documents A and B:
As a result, users may incur into some issues such as:
Objective of this ticket is making sure that once a batch from a range has been deleted, the next round will keep on deleting the same range. One solution could be to loop within the deletion task as long as the number of deleted documents for the range is greater than zero. |
| Comments |
| Comment by Githook User [ 30/Jun/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit f44581d5bfe275a3b9f0454dd7843c04ccfd1f2d) |
| Comment by Githook User [ 28/Jun/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit f44581d5bfe275a3b9f0454dd7843c04ccfd1f2d) |
| Comment by Githook User [ 10/Jun/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit f44581d5bfe275a3b9f0454dd7843c04ccfd1f2d |
| Comment by Githook User [ 07/Jun/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |
| Comment by Pierlauro Sciarelli [ 31/May/22 ] |
|
kaloian.manassiev@mongodb.com observed that also without withDelayBetweenIterations the range deletion gets rescheduled behind the others. Either we made a wrong assessment at the time of closing the ticket, either something has changed and the executor is now yielding. Reopening the ticket so that we don't forget to double-check. |
| Comment by Allison Easton [ 28/Mar/22 ] |
|
This ticket was solved by |