[SERVER-64108] Refreshing the Routing Information only when we hit a targeting error Created: 02/Mar/22  Updated: 18/Oct/23  Resolved: 18/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: RECOVERING-PM-1633
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-49701 Make enableFinerGrainedCatalogCacheRe... Blocked
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2022-03-07, Sharding EMEA 2022-03-21, Sharding EMEA 2022-04-04
Participants:

 Description   

the goal of this ticket is to recover some of the ideas introduced in PM-1633. 

The default behavior of the CatalogCache is that if someone advanced the TimeInStore, the next call to getRoutingInfo* will fetch those changes from the CSRS. The idea of this ticket will be to only fetch those if after targetting with the cached routing information we get an StaleConfigInfo exception.


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