[SERVER-62214] Use explicit read concern in InitialSyncer and CollectionCloner Created: 21/Dec/21  Updated: 29/Oct/23  Resolved: 18/Jan/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Gabriel Marks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-62713 Ensure internal readers set explicit ... Backlog
is related to SERVER-62664 Use explicit read concern in Sessions... Closed
is related to SERVER-62666 Use explicit read concern in Encrypte... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Security 2022-01-24
Participants:
Linked BF Score: 15

 Description   

When investigating BF-23599, I noticed we use ImplicitDefault read concern to get the top of the oplog and also to read the collection data in the logical initial syncer. Since the default read concern can be changed by the user, we probably want to use an explicit read concern ("local" or "available")

This doesn't cause BF-23599 because the default read concern in that test was already "local".



 Comments   
Comment by Githook User [ 18/Jan/22 ]

Author:

{'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}

Message: SERVER-62214 Replace some internal uses of ImplicitDefault read concern
Branch: master
https://github.com/mongodb/mongo/commit/31a411b86fafc6ca303f697dd0a88d7e32acc483

Generated at Thu Feb 08 05:54:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.