[SERVER-36848] Bumping txnNumber on Session must always abort running transaction with lower txnNumber Created: 24/Aug/18 Updated: 29/Oct/23 Resolved: 08/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | disabled-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Sharding 2018-10-08, Sharding 2018-10-22 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 21 | ||||||||||||||||
| Description |
|
If a transaction with a higher txnNumber is started, but it fails validation and uasserts in TransactionParticipant::beginOrContinue() prior to aborting the previous transaction, then the txnNumber on the Session will be the new value, but there will still be an in-progress transaction in TransactionParticipant. The in-progress transaction is no longer accessible, since the txnNumber on Session has been bumped, so a client cannot abort it. We should never bump the txnNumber on Session without aborting the previous transaction. |
| Comments |
| Comment by Githook User [ 08/Oct/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: Revert " This reverts commit ebb653a9bdcb6ba1f1d4cc8113d32cdb86e6d2bb. |
| Comment by Githook User [ 29/Aug/18 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |
| Comment by Tess Avitabile (Inactive) [ 24/Aug/18 ] |
|
Assigning to the Sharding team, since this is a result of the Session refactor. |