-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
Fully Compatible
-
ALL
-
v4.4
-
Sharding 2020-04-06
The replication subsystem should always want to do local read concern on the oplog (with the exception of change streams), however, we've detected at least two points where is set to default:
- On the sync_source_resolver
- On the initial_syncer
This issue can be seen clearly if the read and write concern defaults are set after the logical session cache refresh on a replica set.
Investigate on these points and if there are others that should also be local.
- is caused by
-
SERVER-45692 Ensure all internal inter-node commands which accept read/write concern explicitly specify it
- Closed
- is depended on by
-
SERVER-44745 Trigger a logical session cache refresh for core passthrough suites using the MongoDFixture before running tests
- Closed