Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-1852

Failure during CommitTransaction still moves state to Committed

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 1.5.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed

      During a transaction, if a CommitTransaction times out, the client session state is still moved to "Committed".

      This is inaccurate, as the operations within the commit will not have actually reached the server, so the transaction is not "Committed". Furthermore, if users attempt to abort the transaction when the CommitTransaction fails, they will encounter a "cannot call abortTransaction after calling commitTransaction" error, which is likely an unexpected error.

      The issue is likely here, where we set session state to "Committed" without checking for potential errors from operation execution.

            Assignee:
            benji.rewis@mongodb.com Benji Rewis (Inactive)
            Reporter:
            benji.rewis@mongodb.com Benji Rewis (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: