[SERVER-81303] Make dbCheck default write concern majority Created: 21/Sep/23 Updated: 28/Dec/23 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: | Xuerui Fa | Assignee: | Moustafa Maher |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-855-milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Repl 2023-12-11 | ||||
| Participants: | |||||
| Linked BF Score: | 20 | ||||
| Description |
|
The current default wc for dbCheck is w: 1. This has the potential to flood the oplog, which may increase secondary lag. We should consider using implicitDefaultWC or CWWC if it is set by default for dbCheck to match any other write without an explicit write concern, which will naturally flow control dbCheck to not starve regular writes. |
| Comments |
| Comment by Githook User [ 08/Dec/23 ] |
|
Author: {'name': 'Moustafa Maher Khalil', 'email': 'm.maher@mongodb.com', 'username': 'moustafamaher'}Message: GitOrigin-RevId: 7781dfb4f2988164ec34cd0b0b82421d5b192216 |