[SERVER-62669] Refactor waitForWriteConcern calls in Shard Merge Created: 14/Jan/22  Updated: 27/Oct/23  Resolved: 03/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Gone away Votes: 0
Labels: shard-merge-milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-61134 Call voteCommitMigrationProgress with... Closed
Assigned Teams:
Serverless
Participants:

 Description   

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.



 Comments   
Comment by Suganthi Mani [ 03/Mar/23 ]

Simplified by making all the state doc writes as w:majority.

Generated at Thu Feb 08 05:55:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.