-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Security 2022-01-24
-
15
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".
- is related to
-
SERVER-62664 Use explicit read concern in SessionsCollection
- Closed
-
SERVER-62666 Use explicit read concern in EncryptedDBClientBase and ImplicitEncryptedDBClientBase
- Closed
- related to
-
SERVER-62713 Ensure internal readers set explicit read concerns
- Backlog