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

Make sure implicitlyAbortTransaction is not called when commitTransaction throws in mongos

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      Currently, implicit abort is called on top level command processing. However, it's not ok to send abort when commit was already being processed since some of the shard in the multi-shard transaction might have already committed.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: