[SERVER-84150] Add abort cause to NoSuchTransaction error when transaction was aborted Created: 13/Dec/23  Updated: 18/Dec/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kaitlin Mahar Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: repl-shortlist
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-35411 Add abortCause argument to abortActiv... Backlog
Related
Assigned Teams:
Replication
Participants:

 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.


Generated at Thu Feb 08 06:54:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.