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

Update JS tests' retry logic for Shard Merge

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Serverless

      In tenant_migration_util.js, runTenantMigrationCommand with retryOnRetryableErrors=true will retry "not primary" errors on the donor. But Shard Merge isn't resilient to donor failover. Let's examine all retry logic in tenant_migration_util.js and tenant_migration_test.js and adapt it for Shard Merge.

      This should make BFs easier to diagnose: e.g. if a Shard Merge fails because of donor failover, we want the test to fail right away and log a "not primary" error, instead of timing out after many minutes.

            Assignee:
            backlog-server-serverless [DO NOT USE] Backlog - Server Serverless (Inactive)
            Reporter:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: