[SERVER-35357] Implement a temporary map of transaction runtime states on MongoS Created: 01/Jun/18  Updated: 29/Oct/23  Resolved: 28/Jun/18

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: ShardedTxn:RouterSupport
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-35355 Transaction runtime state participant... Closed
is depended on by SERVER-35364 Track participating shards on the Tra... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-06-18, Sharding 2018-07-02, Sharding 2018-07-16
Participants:

 Description   

In order to be able to make progress on the sharded transactions work before the SessionCatalog is made decorable and made available on mongos, we should just create a simple std::map<LogicalSessionId, TransactionRuntimeState> in order to be able to store per-session transaction information. In order to abstract this temporary map, the API for TransactionRuntimeState should behave like a decoration on OperationContext, even though it might not be one at first.

E.g.: static TransactionRuntimeState* TransactionRuntimeState::get(OperationContext* opCtx);

Should include some basic unit-tests.



 Comments   
Comment by Githook User [ 20/Jun/18 ]

Author:

{'username': 'renctan', 'name': 'Randolph Tan', 'email': 'randolph@10gen.com'}

Message: SERVER-35357 Implement a temporary map of transaction runtime states on MongoS
Branch: master
https://github.com/mongodb/mongo/commit/862bdee50dc0677f6afea73b72913807f7e67265

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