Mongos should always return original error in a transaction

XMLWordPrintableJSON

    • Fully Compatible
    • Sharding 2019-02-11, Sharding 2019-02-25, Sharding 2019-03-11
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When mongos exhausts its retries on retryable errors (e.g. StaleShardVersion, sometimes SnapshotTooOld, etc.) or receives a bad status when aborting on a cleared participant between retries, it will implicitly abort the transaction and throw NoSuchTransaction to return a response with a TransientTransactionError error label to the user. Instead, the original error should always be thrown and the response should continue to generate a TransientTransactionError label.

              Assignee:
              Jack Mulrow
              Reporter:
              Jack Mulrow
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: