Details
-
Bug
-
Resolution: Works as Designed
-
Major - P3
-
None
-
6.0.0-rc0
-
None
-
None
-
Sharding EMEA
-
ALL
Description
SERVER-64979 guarantees that on step-up existing range deletions will be scheduled after resuming a potential deletion that started before stepping down.
However, since the scheduling is done asynchronously, it may happen (even if really improbable) that a migration succeeds and schedules a range deletion before the one being resumed.
Purpose of this ticket is to ensure that also the scheduling of new range deletions serializes behind the on getting resumed.
Attachments
Issue Links
- depends on
-
SERVER-65540 Build range deleter service
-
- Closed
-