[SERVER-67695] Remove the write-blocking mode of dbCheck Created: 30/Jun/22 Updated: 29/Oct/23 Resolved: 03/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | louis-preferred | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||
| Sprint: | Execution Team 2022-09-19, Execution Team 2022-10-03, Execution Team 2022-10-31, Execution Team 2022-11-14 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 157 | ||||||||||||||||
| Description |
|
The point-in-time snapshot mode of dbCheck (the default) seems to have been working well. Given that the default history window is 5 minutes, there is less of a risk of secondaries not having enough history to support a timestamped read in the past. This was more of a concern in 4.4 where the window was 5 seconds. We should remove support for the version that uses MODE_S locks and blocks writes, since it does not appear to be in active use. |
| Comments |
| Comment by Githook User [ 04/Nov/22 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |
| Comment by Githook User [ 03/Nov/22 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: This removes the snapshotRead:false option to dbCheck which blocked concurrent writes |