[SERVER-85651] Collection routing info targeter might invalidate catalog cache entry when it shouldn't Created: 24/Jan/24  Updated: 25/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Participants:
Story Points: 1

 Description   

After SERVER-60144 an invalidation of the catalog cache entry for the original namespace was added in the routing info targeter in case there is a stale info thrown by a shard because a timeseries collection was created under the original namespace while the command was on route. The problem with this approach is that we could be covering other type of errors in the code if the stale namespace received is not a timeseries.

We should take an approach similar to SERVER-84368 and invalidate the cache ONLY if the stale namespace received in the error is a timeseries namespace.


Generated at Thu Feb 08 06:58:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.