-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19, CAR Team 2024-03-04, CAR Team 2024-03-18, CAR Team 2024-04-01, CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-07-22, CAR Team 2024-08-05, CAR Team 2024-08-19, CAR Team 2025-01-06
-
(copied to CRM)
-
3
Currently the sharding catalog cache eviction policy is LRU with a hardcoded capacity of 10k entries. There are some improvements we could consider:
- Making the capacity configurable.
- Considering the size of the cached entry, which may vary wildly depending on each collection routing table size.
- Being more aggressive in evicting long-unused entries.
- depends on
-
SERVER-84243 Dedicate a catalog cache and loader to the shard role
- Closed
- is related to
-
SERVER-93508 ClusterServerParameterOpObserver should not notify updates to cluster parameter values while operating in Initial Sync mode
- Closed