Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-62214

Use explicit read concern in InitialSyncer and CollectionCloner

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      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".

            Assignee:
            gabriel.marks@mongodb.com Gabriel Marks
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: