[SERVER-74754] Clean up uses of WaitForMajorityService::waitForMajority Created: 10/Mar/23  Updated: 29/Oct/23  Resolved: 05/Sep/23

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

Type: Improvement Priority: Major - P3
Reporter: Matthew Russotto Assignee: Evelyn Wu
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after SERVER-74611 Have WaitForMajorityService provide a... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2023-09-04, Repl 2023-09-18
Participants:

 Description   

Prior to SERVER-74611 it wasn't clear whether WaitForMajorityService was waiting for write concern majority (wait for an optime to be made durable on the current primary and a majority of the set, assert on stepdown) or read concern majority (wait for an optime to make it into the majority committed snapshot, regardless of stepdowns). It was in fact write concern majority. SERVER-74611 adds a call to do the same for read concern majority called waitForMajorityForRead. This ticket is to replace old uses of waitForMajority with the new (identical) call waitForMajorityForWrite and remove waitForMajority.



 Comments   
Comment by Githook User [ 31/Aug/23 ]

Author:

{'name': 'Evelyn Wu', 'email': 'evelyn.wu@mongodb.com', 'username': 'evelynwumongo'}

Message: SERVER-74754 Clean up uses of WaitForMajorityService::waitForMajority
Branch: master
https://github.com/mongodb/mongo/commit/3f8d744fb333be9b330e783eff4a02ee24c5faa3

Generated at Thu Feb 08 06:28:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.