[SERVER-38019] Coordinator should not process prepare responses if no longer in state 'waitingForVotes' Created: 08/Nov/18 Updated: 29/Oct/23 Resolved: 08/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.6 |
| Type: | Bug | 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 | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 2018-11-19 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
This fix is not ideal, because it means the coordinator will send abort to all participants who vote abort after the first participant who votes abort. Note, because abortTransaction is sent to and single-shard transactions do not use a two-phase commit, this guarantees that the number of non-voted abort participants in sendAbort will be > 0. |
| Comments |
| Comment by Githook User [ 08/Nov/18 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: |