[SERVER-82589] Move CatalogCache off of the Grid object and onto Service Created: 30/Oct/23  Updated: 15/Dec/23  Resolved: 15/Dec/23

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

Type: Task Priority: Major - P3
Reporter: George Wangensteen Assignee: George Wangensteen
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-84243 Separate Shard-Role Catalog Cache and... In Progress
Sprint: Service Arch 2023-11-13, Service Arch 2023-11-27, Service Arch 2023-12-11, Service Arch 2023-12-25
Participants:

 Description   

Because each cluster-role will have its own CatalogCacheLoader, they will need their own CatalogCaches to load. Move CatalogCache off the shared Grid object and onto the cluster-role aware Service object, so that each role can have its own CatalogCache.



 Comments   
Comment by George Wangensteen [ 15/Dec/23 ]

We've decided that, instead of using the Service object to hold the CatalogCache and CatalogCacheLoaders for router/shard role, we'd like to keep the routing CatalogCache available via the grid, and instantiate a separate, more isolated instance to be used for the very specific/limited needs of the Shard-role. CC Kaloian Manassiev. Closing this in favor of SERVER-84243

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