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

Commands without explicit read concern could skip orphan filtering on secondaries

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • None
    • None
    • Sharding EMEA
    • Fully Compatible
    • ALL
    • Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12

    Description

      The ServiceEntryPoint relies on the presence of the "level" field in "readConcern" to check if shard versioning check is required on secondaries.
      In case an external client didn't set the readConcern because they meant to use the default one (which is "local" since PM-1970) but the command doesn't permit implicit readConcern to be applied the command won't perform orphan filtering on secondary nodes.

      Attachments

        Activity

          People

            allison.easton@mongodb.com Allison Easton
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: