-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
ALL
-
Repl 2021-02-08
Once SERVER-53107 is fixed, tenant_migration_conflicting_donor_start_migration_cmds.js can still fail(i.e, hang)
"Test different cloning read preference", currently starts 2 migration threads concurrently, one with readPreference 'Primary', and another with readPreference 'Secondary'. There are chances the migration with readPreference 'Secondary' thread can start first. If so, the recipient migration fails with "FailedToSatisfyReadPreference error as donor replica set is a single node replica set. The test expects one migration thread to pass and another thread to fail due to ConflictingOperationInProgress. But, in this case, one thread will hang (due to recipient migration failure - FailedToSatisfyReadPreference) and another thread will fail due to ConflictingOperationInProgress.
- related to
-
SERVER-53107 Tenant Migration related jstests should call donorForgetMigration when migration is completed(aborted/committed).
- Closed