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

Make sure implicitlyAbortTransaction is not called when commitTransaction throws in mongos

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Sharding
    • ALL

      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.

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

              Created:
              Updated:
              Resolved: