[SERVER-43139] Investigate _wakeReadyWaiters_inlock() codepaths and remove unnecessary ones Created: 03/Sep/19  Updated: 02/Oct/19  Resolved: 02/Oct/19

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

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

Issue Links:
Depends
depends on SERVER-43135 Introduce a future-based API for wait... Closed
Sprint: Repl 2019-10-07
Participants:

 Description   

Examine codepaths that eventually call _wakeReadyWaiters_inlock() and understand why they are necessary and remove those unnecessary ones.

Ideally, it would be better have a summary/diagram on how last committed optime is set in regards to the ReplSet configuration (e.g. writeConcernMajorityJournalDefault) and when (and why) to wake up replication waiters.



 Comments   
Comment by Lingzhi Deng [ 02/Oct/19 ]

Already addressed in SERVER-43135.

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