Reads from default RWC cache shouldn't reuse user's read concern

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding
    • Sharding 2019-12-30
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Sharding Team
              Reporter:
              Jack Mulrow
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: