[SERVER-36639] Disallow starting a new txn at active txn number if the shard has aborted after being prepared Created: 14/Aug/18  Updated: 29/Oct/23  Resolved: 09/Jan/19

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: ShardedTxn:RouterSupport
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after SERVER-36304 A transaction participant should send... Closed
Related
is related to SERVER-36590 Allow shards to start new transaction... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-12-17, Sharding 2018-12-31, Sharding 2019-01-14
Participants:

 Description   

Currently this state is not tracked by participant shards, but after SERVER-36304 is finished it will be, so when beginning a new transaction at the active transaction number shards should error if they are in the abort after prepare state.



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

Author:

{'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow'}

Message: SERVER-36639 Disallow restarting txn at active txn number if shard has aborted after being prepared
Branch: master
https://github.com/mongodb/mongo/commit/0c8e948f50cec99860e4ac0d15ba76f33512c9d2

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