Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
Description
Prior to this ticket, commitTransaction for a sharded transaction waited for the commitment to complete on all participant shards before returning to the client. After this ticket, commitTransaction will return to the client as soon as the commit decision is persisted with the user's requested writeConcern. This behavior can be configured via the server parameter "coordinateCommitReturnImmediatelyAfterPersistingDecision".
Note that some component writes will still be performed with writeConcern
Unknown macro: {w}.
Description of Linked Ticket
As a first step, coordinateCommit will wait for commit to complete entirely before returning to the client. As an optimization (this ticket), we should return to the client as soon as the commit decision is persisted, in which case the decision may roll back after being reported to the client.
Note, the decision will still be uniform across all two-phase commit participants.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
SERVER-37364 Coordinator should return the decision to the client as soon as the decision is durable
-
- Closed
-