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.
- depends on
-
SERVER-67385 Range deletion tasks may be wrongly scheduled before ongoing queries on range finish on a shard primary
-
- Closed
-
- is depended on by
-
SERVER-65558 Enable Feature flag for PM-2849
-
- Closed
-