SERVER-58991 introduces a new failpoint migrationRecipientFailPostCommitRefresh with semantics analogous to doNotRefreshRecipientAfterCommit. Because this new failpoint does not exist in 5.0 binaries, tests that are run on multiversion suites need to account for it's possible non-existence.
This ticket is to remove this relaxation after 6.0 has been released. At this point, multiversion tests will always run on binaries that support the new failpoint.
- related to
-
SERVER-58991 Acquire the critical section on the recipient shard of a moveChunk operation
- Closed