[SERVER-62806] Allow finer grained refreshes on the catalog cache to get the index catalog Created: 20/Jan/22  Updated: 06/Dec/22  Resolved: 04/Oct/22

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

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: PM-2583-Milestone-2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Participants:

 Description   

The purpose of this ticket is to separate the 3 types of refresh that can happen in the catalog cache given a shard version:

  • Chunk change: will only get changed chunks
  • Index change: will only get changed indexes
  • Full change: Full refresh, will get chunks and indexes

The intention of this ticket is to not penalize chunk refreshes (which will be expected to be more frequent than index refreshes) by querying another collection (the index collection) unless it is necessary.



 Comments   
Comment by Allison Easton [ 04/Oct/22 ]

This will automatically happen because of how advanceTimeInStore works in the ReadThroughCache

Generated at Thu Feb 08 05:56:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.