[SERVER-37841] multi_statement_transaction_all_commands.js appears to only run single statement transactions Created: 30/Oct/18 Updated: 29/Oct/23 Resolved: 14/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.1.4 |
| Fix Version/s: | 4.1.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:Testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2018-11-19 | ||||||||
| Participants: | |||||||||
| Description |
|
Each state transition is currently wrapped in autoRetryTxn, which tries to start the transaction. This has a side effect of aborting the current active transaction. So there is always only one statement that was executed on the current transaction when the state machine transitions to commitTxn. |
| Comments |
| Comment by Githook User [ 14/Nov/18 ] |
|
Author: {'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}Message: |
| Comment by Randolph Tan [ 30/Oct/18 ] |
|
I have confirmed this is actually happening for threadCount = 1 case. |