-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
v6.0, v5.3, v5.0
-
Sharding EMEA 2022-05-30
In SERVER-58466 we introduced an optimization on the lookup function of the CatalogCache to avoid building a new ChunkManager if this object is going to be the same than the one we had before.
However, I forgot to also log a line stating that the refresh was completed. This log line is very useful for debugging purposes, so I propose to add it. The same applies for the update of the stats.
This fix will have to be backported to 6.0 but not to 5.0: the optimization was not backported to that version.
- is caused by
-
SERVER-58466 Minor optimization on the CatalogCache: do not create a new routing table if the collection version hasn't changed
- Closed