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

XMLWordPrintableJSON

    • Replication
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: