moveChunk can fail when the recipient checks for missing indexes and sees that the collection is non-empty because there are orphaned documents that have not been cleaned up.
- depends on
-
SERVER-45024 Refactor the CollectionRangeDeleter to remove dependency on MetadataManager
- Closed
-
SERVER-45179 Add the FCV 4.4 behavior to the MigrationDestinationManager
- Closed
- is duplicated by
-
SERVER-45606 Remove unused 'epoch' parameter in CollectionShardingRuntime::waitForClean
- Closed
- related to
-
SERVER-57743 setFCV 4.4 can take at least orphanCleanupDelaySecs if it starts while there is an in-progress migration for config.system.sessions
- Closed