[SERVER-66659] Abort internal transactions for the previous txnNumber when starting a new txnNumber Created: 23/May/22 Updated: 29/Oct/23 Resolved: 09/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc10, 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding NYC 2022-05-30, Sharding NYC 2022-06-13 |
| Participants: |
| Description |
|
Currently, the TransactionParticipant does not abort internal transactions for the previous txnNumber (i.e. retryable internal transactions) when starting a new txnNumber like it does for regular transactions. Those dangling in-progress transactions should not lead to any hang but they hold on to some resources so we may want to abort them. |
| Comments |
| Comment by Githook User [ 09/Jun/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit bc385b8dcb5b7a550cefaada9d44bc9ded5164de) |
| Comment by Githook User [ 09/Jun/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |