[SERVER-44563] Isolate isMajorityCommittedRead waiter and regular OpTime waiter Created: 11/Nov/19  Updated: 29/Oct/23  Resolved: 06/Dec/19

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

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-50519 resumable index build hangs waiting f... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-12-02, Repl 2019-12-16
Participants:

 Description   

ReplicationCoordinatorImpl::_waitUntilOpTime handles both majority RC waiters and regular optime waiters. But this while loop, this predicates for waiting on a condVar and optime waiters using future make the waiting logic overcomplicated and very hard to reason about. We should consider isolating those two and get rid of the while loop.



 Comments   
Comment by Githook User [ 06/Dec/19 ]

Author:

{'name': 'Lingzhi Deng', 'username': 'ldennis', 'email': 'lingzhi.deng@mongodb.com'}

Message: SERVER-44563: Isolate isMajorityCommittedRead waiter and regular OpTime waiter
Branch: master
https://github.com/mongodb/mongo/commit/d78c2f80751777ddcd4ebd1148c0c7a482b53e63

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