Use --oplogMinRetentionHours in tenant_migration_multi_writes.js to prevent the oplog from being truncated

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.3.0, 5.2.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v5.2
    • Server Serverless 2021-12-27
    • 49
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      tenant_migration_multi_writes.js is a stress test that runs a ton of writes during tenant migrations, and it's possible for the donor's oplog to get truncated out from under the recipient's oplog fetcher. If this happens, the migration will abort before hitting abortTenantMigrationBeforeLeavingBlockingState and so we'll time out waiting to hit this failpoint. We can use the --oplogMinRetentionHours storage option to prevent the oplog from being truncated.

            Assignee:
            Janna Golden
            Reporter:
            Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: