Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
Fully Compatible
-
Sharding EMEA 2021-05-03, Sharding EMEA 2021-05-17
-
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.
Attachments
Issue Links
- depends on
-
SERVER-56469 The shard server catalog cache loader should replace the entries on config.cache.collections and not just update them
-
- Closed
-
-
SERVER-53861 Implement stop migrations procedure for DDL operations
-
- Closed
-
-
SERVER-55146 Bump collection version on any modification of config.collections reshardingFields or allowMigrations fields
-
- Closed
-