Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-53109

Fix tenant_migration_conflicting_donor_start_migration_cmds.js from "FailedToSatisfyReadPreference" failures.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • ALL
    • Repl 2021-02-08

    Description

      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.

      Attachments

        Activity

          People

            lingzhi.deng@mongodb.com Lingzhi Deng
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: