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

Coordinator should return the decision to the client as soon as the decision is durable

    • Fully Compatible
    • Sharding 2018-11-05, Sharding 2020-04-20, Sharding 2020-05-04, Sharding 2020-05-18
    • 0

      Currently, the coordinator waits for all participants to ack the decision before returning the decision to the client.

      Once a participant with a prepared transaction blocks requests with a higher transaction number rather than return PreparedTransactionInProgress (SERVER-38028), the coordinator can return to the client as soon as the commit decision is persisted (with the user's requested writeConcern, including journaling preference).

      Note that if the user requested w:1 writeConcern, the decision may roll back after being reported to the client, but regardless all participants will apply the same decision.

            cheahuychou.mao@mongodb.com Cheahuychou Mao
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            0 Vote for this issue
            14 Start watching this issue