Adapt and re-enable tests that use the failpoint migrationRecipientFailPostCommitRefresh

XMLWordPrintableJSON

    • Cluster Scalability
    • Fully Compatible
    • v9.0
    • ClusterScalability 22Jun-6Jul, ClusterScalability 6Jul-20Jul
    • 200
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      Once moveRange started committing authoritative (introduced in SERVER-127953), we had to disable all those tests that used the failpoint 'migrationRecipientFailPostCommitRefresh'. That failpoint was mostly use to skip the refresh during the release of the critical section, most of the times to reproduce a StaleConfig error on the succeeding command. However, this doesn't make sense any more because, with authoritative commits, the metadata is not cleared when the critical section is released.

      The goal of this task is to adapt all the tests that use this failpoint and enable them. You'll find all the tests lying under this category marked with a TODO pointing to this ticket,

            Assignee:
            Brett Nawrocki
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: