[SERVER-61085] [Upgrade/downgrade] Do not persist txnRetryCounter if value is default Created: 28/Oct/21  Updated: 29/Oct/23  Resolved: 20/Jan/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.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:
Depends
is depended on by SERVER-61088 [Upgrade/downgrade] Make transaction ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-11-29, Sharding 2021-12-13, Sharding 2021-12-27, Sharding 2022-01-10, Sharding 2022-01-24
Participants:
Story Points: 2

 Description   
  • Make the OperationContext not set the txnRetryCounter for multi-document transactions to 0 by default. That is, if the client does not provide a txnRetryCounter, its value should be on the OperationContext boost::none. 
  • Make TransactionParticipant and TransactionCoordinator have a way to track if the txnRetryCounter of multi-document transaction is client-specified or the default. 

This is required by SERVER-61088 where we only want to persist txnRetryCounter if the txnRetryCounter is initialized.



 Comments   
Comment by Githook User [ 19/Jan/22 ]

Author:

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

Message: SERVER-61085 Do not persist txnRetryCounter if value is default
Branch: master
https://github.com/mongodb/mongo/commit/6a08c23ebeab0e0434226cbc6c690b458e61d745

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