[SERVER-34457] readConcern parse failure on start of multi-statement transaction should immediately abort transaction Created: 13/Apr/18  Updated: 27/Oct/23  Resolved: 17/Apr/18

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

Type: Improvement Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Backlog - Replication Team
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

If the readConcern specified on the first statement fails to parse, we return an error, but leave the transaction open and _txnResourceStash empty. When we receive another operation in the same transaction, we find that _txnResourceStash is empty and abort the transaction, returning NoSuchTransaction. It would be preferable to immediately abort the transaction when readConcern fails to parse. Similarly for other errors encountered prior to unstashTransactionResources().


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