Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
Catalog and Routing
Description
Today, it gets replaced with a new one after the refresh finishes. Which means that it can hold to an old copy for the entire duration of the refresh, and potentially delaying it's destruction unnecessarily.
Attachments
Issue Links
- depends on
-
SERVER-78495 Throw out vestiges of enableFinerGrainedCatalogCacheRefresh from the router role
-
- In Code Review
-
- is depended on by
-
SERVER-49701 Make enableFinerGrainedCatalogCacheRefresh default back to true
-
- Blocked
-
- is related to
-
SERVER-50014 Mongos can accumulate ChunkManager of dropped collections no longer being used
-
- Closed
-