[SERVER-42820] Improve error message when transaction is killed due to exceeding timeout Created: 14/Aug/19  Updated: 06/Dec/22  Resolved: 14/Aug/19

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

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-42821 Improve error message when transactio... Closed
Assigned Teams:
Sharding
Participants:

 Description   

Transactions which are alive for too long are killed by the server's session management code (owned by the sharding team). Testing shows that this scenario can produce the following unclear error message:

Exec error resulting in state DEAD :: caused by :: operation was interrupted: generic server error

The former part of the message ("Exec error resulting in state DEAD") is context produced by query execution code. This error string has already been improved in SERVER-38316 and SERVER-41996. The latter part of the error message ("operation was interrupted: generic server error") describes the underlying cause of the error and is produced by the session/transaction management code. This message should be improved to indicate the reason for interruption (e.g. "transaction exceeded transactionLifetimeLimitSeconds").


Generated at Thu Feb 08 05:01:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.