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

TransactionRouter shouldn't lose original non internally retryable snapshot and stale version errors

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.1.7
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2018-12-17

    Description

      The TransactionRouter re-throws non internally retryable snapshot and stale database/shard version errors in a transaction with the NoSuchTransaction error code for consistency with the other causes of the TransientTransactionError label. This makes debugging failures more difficult however, because the original error is not returned to the client. Instead the final error message should include the original error's context.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: