Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-58115

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

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 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

      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@mongodb.com Antonio Fuschetto
            Reporter:
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: