[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: |
|
||||||||||||||||||||
| 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: Getter methods of the CatalogCache that require a refresh don't |