[SERVER-45215] Reads from default RWC cache shouldn't reuse user's read concern Created: 17/Dec/19  Updated: 27/Oct/23  Resolved: 06/Mar/20

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Gone away Votes: 0
Labels: PM-900-Fallout
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-44978 Make ReadThroughCache support asynchr... Closed
Assigned Teams:
Sharding
Sprint: Sharding 2019-12-30
Participants:

 Description   

As of SERVER-43720, the ReadWriteConcernDefaults cache reuses a command's operation context to look up the latest defaults from config.settings. This read currently does not modify the read concern or read source of the operation context, but should instead always read from the latest snapshot to see the most recent defaults. This can possibly be done by using a ReadSourceScope object (introduced by SERVER-40053 and used when fetching a transaction's history) or an AlternativeClientRegion.



 Comments   
Comment by Kaloian Manassiev [ 06/Mar/20 ]

Gone away as a result of SERVER-44978.

Comment by Kevin Pulo [ 17/Dec/19 ]

This might go away naturally if the lookup()s are done on a separate thread, as suggested on SERVER-44978.

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