[SERVER-38215] consider making txn_override.js also retry transaction after getting a TransientTransactionError errorLabel Created: 20/Nov/18  Updated: 29/Oct/23  Resolved: 07/Jan/19

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

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-38847 Suites using txn_override.js will not... Closed
Related
related to SERVER-43491 Specify that jstest only guarantees c... Closed
is related to SERVER-38936 Create unittests for txn_override.js Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-01-14
Participants:
Linked BF Score: 7

 Description   

Currently, it only appears to retry only when commitTransactions returns that errorLabel or when it is already in the middle of "retrying". Here's an example of such a response:

{
  "errorLabels" : [
    "TransientTransactionError"
  ],
  "operationTime" : Timestamp(1542746459, 1),
  "ok" : 0,
  "errmsg" : "Unable to acquire lock '{5511606377568395677: Database, 899920359141007773}' within a max lock request timeout of '5ms' milliseconds.",
  "code" : 24,
  "codeName" : "LockTimeout",
}



 Comments   
Comment by Githook User [ 07/Jan/19 ]

Author:

{'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow'}

Message: SERVER-38215 Retry on transient transaction errors inside txn_override.js
Branch: master
https://github.com/mongodb/mongo/commit/b94945a1ee8d8d65c12fb4a8d53a82b1204c3e54

Generated at Thu Feb 08 04:48:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.