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

Make sure that commitTransaction waits for writeConcern after a read-only transaction

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2018-04-23, Repl 2018-05-07
    • 18

      A read-only transaction running at speculative majority or speculative snapshot will read its data from the most recent snapshot. It then will need to wait at commit time to ensure that the data it read is committed. We can do this by remembering the optime that the read transaction started with and then setting the last OpTime on the Client object to that optime in the commitTransaction command body.

            Assignee:
            matthew.russotto@mongodb.com Matthew Russotto
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: