[SERVER-38035] TransactionRouter should not implicitly send abortTransaction once it has sent coordinateCommit to the coordinator Created: 08/Nov/18 Updated: 29/Oct/23 Resolved: 12/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:DistributedCommit | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-11-19 |
| Participants: |
| Description |
|
Otherwise, the coordinator may make a commit decision and the commitTransactions from the coordinator can race with the abortTransactions from the router. |
| Comments |
| Comment by Githook User [ 12/Nov/18 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: |