Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13283

Investigate changes in SERVER-37364: Allow transactions that use two-phase commit to respect lower writeConcern than majority

    XMLWordPrintableJSON

Details

    Description

      Description

      Downstream Change Summary

      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

        Activity

          People

            jason.price@mongodb.com Jason Price
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              2 years, 50 weeks, 1 day ago