[SERVER-34339] Aggregation error aborts the transaction without letting the shell helper know Created: 05/Apr/18 Updated: 06/Dec/22 Resolved: 12/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | Needs Triage |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Steps To Reproduce: | Extract from read_concern_snapshot_aggregation.js |
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| 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`. |
| Comments |
| Comment by Shane Harvey [ 12/Apr/18 ] | ||||||||||||
|
The abortTransaction should ignore the "NoSuchTransaction" error because it means the transaction was already aborted on the server. | ||||||||||||
| Comment by Kyle Suarez [ 12/Apr/18 ] | ||||||||||||
|
It's more than just aggregation. Running a runCommand also gives the same frustrating experience; e.g.:
| ||||||||||||
| Comment by Gregory McKeon (Inactive) [ 09/Apr/18 ] | ||||||||||||
|
ping spencer, this may have gotten missed. |