Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- car-pm-upvote

Assigned Teams:

Catalog and Routing
Sprint:
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, CAR Team 2025-01-20, CAR Team 2025-02-03, CAR Team 2025-02-17, CAR Team 2025-03-03
Case:
Story Points:
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-92699 Implement invalidation policy based on last accessed time for LRU cache

Blocked

SERVER-84243 Dedicate a catalog cache and loader to the shard role

Closed

SERVER-100777 Add the ability to change the catalog cache size in runtime

Open

SERVER-100779 Cluster parameters for catalog cache sizing

Blocked

is related to

SERVER-93508 ClusterServerParameterOpObserver should not notify updates to cluster parameter values while operating in Initial Sync mode

Closed

Assignee:: Unassigned

Reporter:: Jordi Serra Torrens

Participants:: Jordi Serra Torrens, Sergi Mateo Bellido, Sulabh Mahajan

Votes:: 0 Vote for this issue

Watchers:: 16 Start watching this issue

Created:: Nov 02 2023 03:03:19 PM UTC

Updated:: Feb 20 2025 02:17:21 PM UTC