Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
Replication
-
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
-
SERVER-39364 Audit uses of setLastOpToSystemLastOpTime
-
- Closed
-
- related to
-
SERVER-39489 Clarify optime creation in TransactionParticipant
-
- Closed
-