[SERVER-43135] Introduce a future-based API for waiting for write concern Created: 03/Sep/19  Updated: 29/Oct/23  Resolved: 02/Oct/19

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

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:
Depends
is depended on by SERVER-43139 Investigate _wakeReadyWaiters_inlock(... Closed
is depended on by SERVER-43307 Avoid checking _checkIfWriteConcernCa... Closed
is depended on by SERVER-43417 Signal the flusher thread to flush in... Closed
Duplicate
is duplicated by SERVER-40250 High contention for ReplicationCoordi... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-09-09, Repl 2019-09-23, Repl 2019-10-07
Participants:

 Description   

Also:

  • refactor the existing Waiter and WaiterList API and unify ThreadWaiter and CallbackWaiter into a future-based waiter class.
  • optimize ReplicationCoordinatorImpl::_wakeReadyWaiters_inlock to minimize unnecessary wake-ups by ordering waiters by OpTime.


 Comments   
Comment by Githook User [ 02/Oct/19 ]

Author:

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

Message: SERVER-43135: Introduce a future-based API for waiting for write concern
Branch: master
https://github.com/mongodb/mongo/commit/db4a142a48ccf757e8eeb89485bec28957c3d789

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