Refactor waitForWriteConcern calls in Shard Merge

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Serverless
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      TenantMigrationDonorService and TenantMigrationRecipientService each wait for write concern in various places after updating a state document or other data. Sometimes they wait for majority, sometimes for w: 1. Let's audit these, wait for the weakest write concern possible everywhere, and refactor these code blocks.

              Assignee:
              [DO NOT USE] Backlog - Server Serverless (Inactive)
              Reporter:
              A. Jesse Jiryu Davis
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: