[SERVER-39973] Router should not decide to use recovery commit path based on whether participant list is empty Created: 05/Mar/19  Updated: 29/Oct/23  Resolved: 06/Mar/19

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

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-03-11
Participants:
Linked BF Score: 19

 Description   

Currently the router checks if the participant list is empty, which will be true on the first recovery commitTransaction attempt, but the recovery commit path actually creates and adds the recovery shard as a participant, so on another recovery commitTransaction attempt, the router will use the single-shard commit path instead of the recovery commit path.



 Comments   
Comment by Githook User [ 08/Mar/19 ]

Author:

{'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}

Message: SERVER-39973 Follow-up fix to prevent router from crashing if startTransaction is sent on commitTransaction
Branch: master
https://github.com/mongodb/mongo/commit/71bb13f2885036a229882ebb41ac4a0640ac2800

Comment by Githook User [ 06/Mar/19 ]

Author:

{'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}

Message: SERVER-39973 Router should not decide to use recovery commit path based on whether participant list is empty
Branch: master
https://github.com/mongodb/mongo/commit/9bbce9db3d4a3ba73fb26cf32ffd5d8ecbe7e08b

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