[SERVER-80332] Fix incorrect step accounting in transaction coordinator server status Created: 23/Aug/23 Updated: 29/Jan/24 Resolved: 29/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 8.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ivan Fefer | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-8, Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5 |
| Participants: | |
| Story Points: | 3 |
| Description |
|
When we move transaction coordinator to the next step, we increment the count of coordinators in the new step and decrement the count for the previous step. However, in case of error during kWritingParticipantList, we will jump straight to
|
| Comments |
| Comment by Githook User [ 29/Jan/24 ] |
|
Author: {'name': 'Janna Golden', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message:
GitOrigin-RevId: 662b97f08dfb6ea4d6f97db9f16ea1b2b349a188 |