[SERVER-82588] Move CatalogCacheLoader to be a decoration on 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: James Bronsted
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-83433 Add back the test coverage for runnin... Backlog
Related
related to SERVER-83997 Add awareness of assigned ClusterRole... Backlog
related to SERVER-84243 Separate Shard-Role Catalog Cache and... In Progress
related to SERVER-84247 Complete TODO listed in SERVER-82588 Closed
Assigned Teams:
Service Arch
Sprint: Service Arch 2023-11-27, Service Arch 2023-12-11, Service Arch 2023-12-25
Participants:

 Description   

Until the ShardServerCatalogCacheLoader is removed, the shard and router roles require different implementations of the CatalogCacheLoader. To enable this, we will need to remove the CatalogCacheLoader to be a decoration on the cluster-role-aware Service object, to provide each role with its own implementation.



 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@mongodb.com. 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.