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

Add abort cause to NoSuchTransaction error when transaction was aborted

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Replication

    Description

      In the case where we return NoSuchTransaction due to the transaction having been aborted, it would be helpful to users to be able to see the reason why (e.g. the transaction exceeded TransactionLifetimeLimitSeconds). This can be useful for e.g. large batched writes where the transaction ends up getting aborted by the periodic cleanup job in between batches.

      https://github.com/mongodb/mongo/blob/4d37b895673cd4140afa8368fa4e2b1703b59f94/src/mongo/db/transaction/transaction_participant.cpp#L2508-L2511

      I think SERVER-35411 would make solving this issue easy so I am linking it, but it's possible we can provide this information in some other way without doing that ticket.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            kaitlin.mahar@mongodb.com Kaitlin Mahar
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated: