[SERVER-68660] Make range deleter service observer register tasks with ongoing queries future Created: 09/Aug/22 Updated: 29/Oct/23 Resolved: 16/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Silvia Surroca |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding EMEA 2022-08-22, Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The range deleter service observer is currently registering tasks (here and here) by relying on the default value of waitForActiveQueriesToComplete. Purpose of this ticket is to register the tasks by passing the proper future that gets marked as ready once ongoing queries retaining the range are finishing. As part of this ticket, remember to featureflag the "wait for clean" happening in the migration destination manager: if the feature flag is active, invoke getOverlappingRangeDeletionsFuture and wait on it for at most rangeDeletionWaitDeadline , else keep on invoking waitForClean. |
| Comments |
| Comment by Githook User [ 15/Sep/22 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |