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

Assertion to guard against individual commands inside transactions specifying their own readConcern happens after waiting for readConcern

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.4.0-rc2, 4.7.0
    • None
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-04-20
    • 44

    Description

      We have a uassert that should prevent individual transaction statements from specifying their own readConcern. However, we wait for read concern before calling runCommandImpl, which is where our uassert executes.

      As a result, if we specify a readConcern for a statement following the first statement in the transaction, we will fail the uassert, but not until after actually waiting for the read concern.

      Attachments

        Issue Links

          Activity

            People

              maria.vankeulen@mongodb.com Maria van Keulen
              maria.vankeulen@mongodb.com Maria van Keulen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: