[SERVER-40467] Make sure implicitlyAbortTransaction is not called when commitTransaction throws in mongos Created: 03/Apr/19  Updated: 27/Oct/23  Resolved: 04/Apr/19

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

Currently, implicit abort is called on top level command processing. However, it's not ok to send abort when commit was already being processed since some of the shard in the multi-shard transaction might have already committed.



 Comments   
Comment by Randolph Tan [ 04/Apr/19 ]

implicitlyAbort already checks to make sure not to send abort when commit already started

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