Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
Needs Triage
-
None
-
Replication
-
ALL
-
Description
Error due to aggregation not supporting snapshot reads will abort the transaction. So if we commit/abort the transaction from the shell helper, we will get an “transaction has been aborted” error. And the shell helper doesn’t know about the abort, so starting a new transaction triggers an error: `There is already an active transaction on this session`.
I think the fix would be either handling the aggregation error differently or letting shell helper end the transaction quietly with commit/abortTransaction even when there is an "transaction has been aborted" error.
Attachments
Issue Links
- duplicates
-
SERVER-34441 Error when aborting/committing a nonexistent txn or starting a txn with one running
-
- Closed
-
- is depended on by
-
SERVER-34094 Change snapshot read tests to use multi-statement transactions
-
- Closed
-
-
SERVER-34388 Continue converting snapshot reads test to use multi-statement txn api
-
- Closed
-