-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Repl 2019-10-07
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.
- depends on
-
SERVER-43135 Introduce a future-based API for waiting for write concern
- Closed