[SERVER-37245] Use the SessionCatalog to track sessions in MongoS Created: 21/Sep/18  Updated: 29/Oct/23  Resolved: 19/Nov/18

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

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

Issue Links:
Depends
depends on SERVER-36799 Move transaction related functionalit... Closed
Duplicate
is duplicated by SERVER-36471 Refactor parts of SessionCatalog and ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-10-08, Sharding 2018-10-22, Sharding 2018-11-19
Participants:

 Description   

Once all the MongoD transaction functionality is moved out of the SessionCatalog, this ticket is to start using the simplified SessionCatalog on MongoS instead of the temporary map we put there.



 Comments   
Comment by Githook User [ 19/Nov/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-37245 Use the SessionCatalog to track sessions on MongoS
Branch: master
https://github.com/mongodb/mongo/commit/55478ba4a5bcbbff6c4fe500974e636914c41cae

Comment by Githook User [ 19/Nov/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-37245 Do not access the SessionCatalog directly if not necessary

The session catalog should not be accessed directly by majority of the
consumers on mongod or mongos, instead they should interact with it
through the decorations, which properly validate that the session has
been assigned to the OperationContext.
Branch: master
https://github.com/mongodb/mongo/commit/c131f5903c8b4039d3fb2732142c987e296bd503

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