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

Transaction participants don't need to do a noop write before committing a read-only transaction

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible

      Description

      Currently, TransactionParticipant::commitUnpreparedTransaction does a noop write after committing a read-only transaction, so that waiting for writeConcern waits for a Timestamp after the transaction's read Timestamp, to respect the isolation level requested by the client's writeConcern.

      Instead, it can just wait for writeConcern of the read Timestamp.

        Attachments

          Issue Links

          depends on

          Task - A task that needs to be done. SERVER-39364 Audit uses of setLastOpToSystemLastOpTime

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-39489 Clarify optime creation in TransactionParticipant

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              esha.maharishi Esha Maharishi
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated: