[SERVER-62368] Range deleter must honor rangeDeleterBatchDelayMS Created: 05/Jan/22 Updated: 29/Oct/23 Resolved: 31/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 5.2.1, 4.4.13, 5.0.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v5.2, v5.0, v4.4
|
||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | Unit test proving the erroneous behavior in v4.4 (diff applied on commit 3bdd66d).
|
||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Sharding EMEA 2022-02-07 | ||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||
| Description |
|
The semantic of the rangeDeleterBatchDelayMS parameter changed over time and the original idea of using it to throttle range deletions is not honored in the majority of scenarios. Objective of this ticket is to introduce a global delay applied to the range deletions at thread pool level, independently from collections/ranges. Following, a summary of the current semantics. Versions gte v4.4The delay is applied to the deletion of batches belonging to a specific range. Problem: if there are several (more than one) range deletion tasks scheduled for different collections or for the same collection on different ranges, deletions are actually not throttled. Versions until v4.2The batch delay is per collection and the rescheduling of a cleanup task is not bound to a specific range. Problem: if there are several (more than one) range deletion tasks scheduled for different collections, deletions are actually not throttled. |
| Comments |
| Comment by Githook User [ 03/Feb/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 03/Feb/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 03/Feb/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 31/Jan/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |