[SERVER-76215] Add NoSuchTransaction as an accepted error in internal_transactions_sharded.js concurrency workload Created: 17/Apr/23  Updated: 12/Dec/23

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

Type: Task Priority: Major - P3
Reporter: Jason Zhang Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: cs-subteam1, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Cluster Scalability
Participants:
Linked BF Score: 5

 Description   

Details are in BF-26468, but it's possible that a participant can failover and forget a transaction if we haven't entered prepareTransaction yet.



 Comments   
Comment by Jack Mulrow [ 12/May/23 ]

NoSuchTransaction is a transient error, so the internal transactions in this workload should already be retrying on them. I think the linked BF may actually be a manifestation of SERVER-77053 where the transaction API wasn't retrying on NoSuchTransaction errors with a write concern error.

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