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

Investigate consolidation of readConcern validation

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None

      Description

      Presently, we have validation of readConcern that occurs in a few places in the code. This can lead to some unexpected consequences, such as read concern validation occurring later than expected (see SERVER-47444).
      In some cases, this separation of validation seems unavoidable, e.g., the service entry point level validation versus the strategy.cpp validation, or the validation that must occur on transaction unstash.

      We should investigate whether it's possible to merge the validation that occurs at the service entry point level with the validation that occurs in the replication coordinator, provided that the read concern is not expected to change between these two code locations.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              maria.vankeulen Maria van Keulen
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: