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

Default read concern setting is not being applied to TransactionRouter

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Cluster Scalability
    • ALL
    • 2

    Description

      The transaction router extracts the read concern settings here via beginOrContinue. However, in the command processing, we call beginOrContinue first, before applying the default settings to the operation context's read concern settings

      Attachments

        Activity

          People

            backlog-server-cluster-scalability Backlog - Cluster Scalability
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: