[SERVER-37039] Allow multiple transaction coordinators to exist for a session Created: 06/Sep/18 Updated: 29/Oct/23 Resolved: 15/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:DistributedCommit, transaction-coordinator-management | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-10-08, Sharding 2018-10-22 |
| Participants: |
| Description |
|
This will involve modifying the TransactionCoordinatorService to attempt to abort previous unfinished (and undecided) transactions when a new transaction comes in for that session with a higher transaction number. |