Recently, we found several bugs in cleanupOrphaned through code inspection. Prior to fixing those bugs, it would be useful to write a concurrency test which tested cleanupOrphaned, migrations, and failovers together to see if any of those bugs could have been uncovered that way. Furthermore, we should try to ensure that there are no other bugs lurking before we proceed with fixes for the known bugs. This will also be a good precursor to SERVER-42192 which will add a concurrency workload to test the resumable range deleter.
- is depended on by
-
SERVER-42352 cleanupOrphaned does not respect migration protocol on failover
- Closed
-
SERVER-42360 cleanupOrphaned does not work properly in edge case with concurrent migrations on a shard
- Closed
- related to
-
SERVER-42352 cleanupOrphaned does not respect migration protocol on failover
- Closed
-
SERVER-42360 cleanupOrphaned does not work properly in edge case with concurrent migrations on a shard
- Closed
-
SERVER-42192 Write a concurrency workload to test that orphaned ranges are always deleted and nothing that shouldn’t be deleted gets deleted
- Closed
-
SERVER-43107 Disable random chunk migration failpoint for concurrency with_balancer suites
- Closed