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

TransactionRouter shouldn't implicitly abort after NoSuchTransaction from abortTransaction

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:

      Description

      Currently, mongos will implicitly abort a transaction on ok:0 responses by sending abort to each participant shard unless two phase commit has been started. This means if a client sends abortTransaction explicitly, which also sends abortTransaction to each participant and waits for each to respond before returning, and any shard returns NoSuchTransaction, which may happen if the shard already aborted implicitly or explicitly, the router will re-send abort to each participant, which is unnecessary.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-sharding Backlog - Sharding Team
            Reporter:
            jack.mulrow Jack Mulrow
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: