[SERVER-63543] Investigate how LogicalSessionCacheServer differ on Config and shard server Created: 10/Feb/22 Updated: 04/Oct/22 Resolved: 04/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Shuvalov (Inactive) | Assignee: | Andrew Shuvalov (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding 2022-10-03, Sharding 2022-10-17 |
| Participants: | |
| Story Points: | 2 |
| Description |
|
The LogicalSessionCacheServer have different implementations - SessionsCollectionConfigServer and SessionsCollectionSharded, and it is a singleton. Investigate how session cache is different and how to reconcile this. |