Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.0-rc0, 4.3.6, 4.7.0
Affects Version/s: None
Component/s: Replication, Sharding
Labels:
- sharding-4.4-stabilization

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.4
Sprint:
Sharding 2020-04-06
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Marcos José Grillo Ramirez
Reporter:: Marcos José Grillo Ramirez
Participants:: Githook User, Marcos José Grillo Ramirez
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Mar 23 2020 03:07:08 PM UTC
Updated:: Oct 29 2023 10:10:28 PM UTC
Resolved:: Mar 24 2020 05:48:00 PM UTC
Confidence Status Last Update:: 24/Mar/20 10:55 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates