[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
kWritingDecision, skipping kWaitingForVotes, leading to server status like that 

"currentInSteps" : {
    "writingParticipantList" : NumberLong(1),
    "waitingForVotes" : NumberLong(-1),
    "writingDecision" : NumberLong(1),
    "waitingForDecisionAcks" : NumberLong(0),
    "writingEndOfTransaction" : NumberLong(0),
    "deletingCoordinatorDoc" : NumberLong(0)
}



 Comments   
Comment by Githook User [ 29/Jan/24 ]

Author:

{'name': 'Janna Golden', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-80332 Fix incorrect step accounting in transaction coordinator… (#18191)

SERVER-80332 Fix incorrect step accounting in transaction coordinator
server status

GitOrigin-RevId: 662b97f08dfb6ea4d6f97db9f16ea1b2b349a188
Branch: master
https://github.com/mongodb/mongo/commit/825eab36205c7ed209aa844ad0ada026bf2c536a

Generated at Thu Feb 08 06:43:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.