Outdated information can remain in the catalog cache after a collection is renamed

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.2, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Sharding EMEA 2021-06-28
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Antonio Fuschetto
              Reporter:
              Antonio Fuschetto
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: