[SERVER-41615] Transaction coordinator diagnostics should handle coordinator failover Created: 10/Jun/19 Updated: 29/Oct/23 Resolved: 09/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Lamont Nelson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.2
|
||||||||
| Sprint: | Sharding 2019-08-12, Sharding 2019-08-26, Sharding 2019-09-09 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, if a shard primary fails over while coordinating a two-phase commit, the new primary will create a new TransactionCoordinator to resume the two-phase commit, and the diagnostics it captures will be as if the new primary had coordinated the entire commit. The places with TODO comments in transaction_coordinator.cpp should be updated in a way that makes it clear whether the coordinator was resumed after failover or not. |
| Comments |
| Comment by Githook User [ 10/Sep/19 ] |
|
Author: {'username': 'lamontnelson', 'email': 'lamont.nelson@mongodb.com', 'name': 'Lamont Nelson'}Message: (cherry picked from commit 398471a4fde3cdd7ca57f6bbf601ad66998b1150) |
| Comment by Githook User [ 06/Sep/19 ] |
|
Author: {'username': 'lamontnelson', 'email': 'lamont.nelson@mongodb.com', 'name': 'Lamont Nelson'}Message: |
| Comment by Lamont Nelson [ 05/Sep/19 ] |
|
Not sure why this is closed. |