[SERVER-83092] Eliminate the unnecessary majority check in wait for write concern Created: 09/Nov/23 Updated: 25/Jan/24 Resolved: 08/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Wenbin Zhu | Assignee: | Kishore Devireddy |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-3489-Milestone-MiscImprovement-CP | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Repl 2023-11-27, Repl 2023-12-11 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 5 | ||||||||||||||||||||||||||||
| Description |
|
For majority write concern, in addition to waiting for the committed snapshot to advance past the write, it also waits for a majority of nodes to have their lasDurable (j: true) or lastApplied (j: false) to advance past the write. In fact waiting for the committed snapshot is sufficient in most cases and so the additional wait is usually a no-op and only needed when writeConcernMajorityJournalDefault is false and j: true. We can change it to only perform the additional wait in that particular case. We can also remove the wait for drop pending collections step as part of waiting for majority since that's no longer necessary today. |
| Comments |
| Comment by Kishore Devireddy [ 08/Dec/23 ] |
|
fixed |
| Comment by Kishore Devireddy [ 08/Dec/23 ] |
| Comment by Githook User [ 08/Dec/23 ] |
|
Author: {'name': 'Kishore Devireddy', 'email': 'kishore.devireddy@mongodb.com', 'username': 'kishorekrd'}Message: GitOrigin-RevId: 5899ae739bb03a3ee064271b47e64168f778143b |