Dirty information can be present in the catalog cache after a collection is renamed, leading to data inconsistencies that may impact the correctness of subsequent operations (see SERVER-34632).
The goal is to force a cache refresh just after the collection renaming.
- causes
-
SERVER-58465 Fix the cleanup of the Routing Info in the rename operation
- Closed