-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-08-10
At the moment when looking up a database entry into the catalog cache it is checked if its primary shard still exists, otherwise the database entry is invalidated.
The aim of this task is to move the execution of this invalidation when the shard is actually removed and not when the entry is accessed. In order to do so, CatalogCache::invalidateEntriesThatReferenceShard needs to invalidate also database entries that has that shard as their primary shard.
This can be achieved using _databaseCache.invalidateIfCachedValue() function.
It would be also interesting to see if there is any javascript test that cover this scenario and if there is not to create one.
- causes
-
SERVER-50175 Fix CatalogCache's threadPool shutdown order
-
- Closed
-
- depends on
-
-
- Closed
-
-
-
- Closed
-