[SERVER-37597] voteCommit for an aborted coordinator should send abort to the calling participant Created: 12/Oct/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: | Jack Mulrow | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:DistributedCommit, sharding-wfbf-day, transaction-coordinator-management | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2018-10-22 | ||||
| Participants: | |||||
| Linked BF Score: | 56 | ||||
| Description |
|
The transaction coordinator removes itself from the coordinator catalog when it decides to abort, but it does so through a promise, which requires dropping the coordinator mutex. This allows a voteCommit to be processed by a coordinator in the kAborted state, which currently leads to no action. Instead, this should be treated the same as the non-existent coordinator case (see |
| Comments |
| Comment by Githook User [ 15/Oct/18 ] |
|
Author: {'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com', 'username': 'saltzm'}Message: |