[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: |
|
||||||||
| 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 |