[SERVER-70457] Split session object into RouterSession and ParticipantSession Created: 11/Oct/22  Updated: 28/Dec/23  Resolved: 28/Dec/23

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

Type: Improvement Priority: Major - P3
Reporter: Shin Yee Tan Assignee: Jack Mulrow
Resolution: Won't Do Votes: 0
Labels: sharding-nyc-subteam3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Sprint: Sharding NYC 2022-11-28, Sharding 2022-12-12, Sharding NYC 2022-12-26, Sharding NYC 2023-01-09, Sharding NYC 2023-01-23, Sharding NYC 2023-02-06, Sharding NYC 2023-02-20, Sharding NYC 2023-03-06, Sharding NYC 2023-03-20, Sharding NYC 2023-04-03, Sharding NYC 2023-04-17, Sharding NYC 2023-05-01, Sharding NYC 2023-05-15, Sharding NYC 2023-05-29, Sharding NYC 2023-06-12, Sharding NYC 2023-06-26, Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07, Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27, Cluster Scalability 2023-12-11, Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-8
Participants:

 Description   

TransactionRouterResourceYielder will check in the session from the shard acting as the router. The same shard will check out the session as transaction participant.

If we split the Session object into a RouterSession and ParticipantSession then we wouldn't need to bother with the yielding because the shard acting as a router holding the RouterSession for lsid=abc123 could still freely check out the ParticipantSession for lsid=abc123



 Comments   
Comment by Fausto Leyva (Inactive) [ 11/Oct/22 ]

Hey, we would like to get some input on our summary of the issue. 

Generated at Thu Feb 08 06:16:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.