- 
    Type:Improvement 
- 
    Resolution: Fixed
- 
    Priority:Major - P3 
- 
    Affects Version/s: None
- 
    Component/s: None
- 
        Minor Change
- 
        Execution Team 2022-09-19, Execution Team 2022-10-03, Execution Team 2022-10-31, Execution Team 2022-11-14
- 
        157
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
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.
- is depended on by
- 
                    SERVER-66145 Identify and fix locations that write while holding read tickets -         
- Closed
 
-         
- 
                    SERVER-60621 Investigate if we can ban upgrading the global lock -         
- Closed
 
-