[SERVER-60529] [txnRetryCounter] Make TransactionParticipant take in txnNumberAndRetryCounter instead of txnNumber and txnRetryCounter separately Created: 07/Oct/21  Updated: 29/Oct/23  Resolved: 03/Nov/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Task Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Jason Zhang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-10-18, Sharding 2021-11-01, Sharding 2021-11-15
Participants:
Linked BF Score: 32
Story Points: 2

 Description   

Per this code review commentSERVER-60323 will introduce the type txnNumberAndRetryCounter to force users and implementers of the TransactionCoordinator subsystem to specify both the txnNumber and txnRetryCounter. txnRetryCounter was added to TransactionParticipant and TransactionRouter in SERVER-58752 so those classes should be made to use txnNumberAndRetryCounter as well.



 Comments   
Comment by Githook User [ 03/Nov/21 ]

Author:

{'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}

Message: SERVER-60529 Make TransactionParticipant take in txnNumberAndRetryCounter instead of txnNumber and txnRetryCounter separately
Branch: master
https://github.com/mongodb/mongo/commit/eca169a0b7009a783b0271f81677aadcdfd1a78b

Generated at Thu Feb 08 05:50:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.