[SERVER-54583] Relax implementation of getDatabaseWithRefresh/getCollectionRoutingInfoWithRefresh of the CatalogCache Created: 17/Feb/21  Updated: 29/Oct/23  Resolved: 06/May/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: PM-1965-Cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-56469 The shard server catalog cache loader... Closed
depends on SERVER-53861 Implement stop migrations procedure f... Closed
depends on SERVER-55146 Bump collection version on any modifi... Closed
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-05-03, Sharding EMEA 2021-05-17
Participants:
Linked BF Score: 165

 Description   

The goal of this ticket is to relax the implementation of the getDatabaseWithRefresh and the getCollectionRoutingInfoWithRefresh methods: both of them invalidate an entry in their caches.

Instead of doing that, we could just advanceTimeInStore using a ComparableDatabaseVersion/ComparableChunkVersion with the forcedRefresh flag.

Some tests, for instance this one, will have to be fixed.



 Comments   
Comment by Githook User [ 06/May/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-54583 Relax implementation of getDatabaseWithRefresh/getCollectionRoutingInfoWithRefresh of the CatalogCache

Getter methods of the CatalogCache that require a refresh don't
invalidate the entry on the CatalogCache anymore. Instead of that, we
ask to refresh with a special token that always force a refresh.
Branch: master
https://github.com/mongodb/mongo/commit/23c153fe064a5be9c18c706696bf30acef2ed578

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