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

Tenant migration initial sync tests should prevent TenantMigrationAccessBlocker from transitioning to the next state while the check is being done

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.9
    • Sprint:
      Sharding 2021-04-05
    • Linked BF Score:
      77

      Description

      If the migration hasn't committed when the state doc is read here, the TenantMigrationAccessBlocker check can fail (i.e. time out due to assert.soon) since the migration could continue past the state the check expects. To workaround this, we can either pause the migration or disable replication on the initial sync node so that the TenantMigrationAccessBlocker cannot transition to the next state while the check is being done. Note that we had to do something similar in the startup recovery tests (we used failpoint PrimaryOnlyServiceSkipRebuildingInstances to make the migration not resume after restart).

        Attachments

          Activity

            People

            Assignee:
            cheahuychou.mao Cheahuychou Mao
            Reporter:
            cheahuychou.mao Cheahuychou Mao
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: