[SERVER-41032] TransactionRouter's _isRecoveringCommit field is not reset on receiving a higher transaction number Created: 07/May/19  Updated: 29/Oct/23  Resolved: 15/May/19

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

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-05-20
Participants:

 Description   

I just noticed the _isRecoveringCommit field is set to true here, and checked here, but it's never reset to false.



 Comments   
Comment by Githook User [ 15/May/19 ]

Author:

{'name': 'Matthew Saltz', 'username': 'saltzm', 'email': 'matthew.saltz@mongodb.com'}

Message: SERVER-41032 Properly reset the _isRecoverCommit flag on the TransactionRouter when a new transaction begins
Branch: master
https://github.com/mongodb/mongo/commit/2ca37502214304dddeb90ddac0c24b301ca1518b

Generated at Thu Feb 08 04:56:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.