-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.4.0
-
Component/s: Internal Code
-
None
-
Fully Compatible
-
v4.7, v4.4
-
Execution Team 2020-09-07, Execution Team 2020-09-21
Internal readers should default to using the kNoTimestamp ReadSource. Users of AutoGetCollectionForRead are subject to having their ReadSource changed, which is not always desirable and leads to unexpected behavior.
Since internal readers have a "local" readConcern by default, despite not originating from a command, they are still eligible for changing their ReadSource.
Only reads originating from commands should change their ReadSource.
- is duplicated by
-
SERVER-49781 Setting lastApplied before startup recovery has finished causes race with reconstructing prepared transactions
- Closed
- related to
-
SERVER-80280 Consider introducing concept of draining internal readers after stepdown and before starting secondary oplog application
- Closed
-
SERVER-79955 Need a more complete mechanism for internal readers to avoid fassert when crossing member state PRIMARY to SECONDARY transition
- Closed
-
SERVER-51430 update log message search in recovery_wt_cache_full.js to look at end of oplog application
- Closed