When starting a moveChunk, it should be ensured that there is no unfinished migration pending recovery (even for other collections). Ensuring that will guarantee that there's never more than one document in config.migrationCoordinators.
This prevents the situation that led to SERVER-62245.
- causes
-
SERVER-65371 MigrationSourceManager running on secondary node may trip invariant
- Closed
- is related to
-
SERVER-62245 MigrationRecovery must not assume that only one migration needs to be recovered
- Closed
-
SERVER-60521 Deadlock on stepup due to moveChunk command running uninterrupted on secondary
- Closed