[SERVER-37440] coordinateCommit should fall back to recovering decision from local participant Created: 03/Oct/18 Updated: 29/Oct/23 Resolved: 29/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: | Matthew Saltz (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 | ||||||||||||
| Sprint: | Sharding 2018-11-19, Sharding 2018-12-03 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
If coordinateCommit gets retried due to a network error but the first coordinateCommit call succeeded in committing, we need to make sure that we recover the correct decision so that it may be returned to mongos. This overlaps with the work to be able to recover the commit decision in case of mongos failover, and potentially could replace/remove the need for it. |
| Comments |
| Comment by Githook User [ 29/Nov/18 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: |