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

Refresh the CatalogCache before dropping the local collection

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.15, 6.0.4, 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • ALL
    • v6.2, v6.0, v5.0
    • Sharding EMEA 2022-12-12

      The goal of this task is to change how sharded local collections are dropped. We can see this function as a sequence of three operations:

      1. Clear the in-memory filtering metadata.
      2. Dropping the local Collection.
      3. Clearing the routing information (in-memory and persisted (i.e. config.cache.*)).

      The idea is to swap 2 and 3, so we clear the routing information first and then we drop the local collection, so if the collection to be dropped doesn't exist on that shard (i.e. in this path we throw an exception that is captured in an upper level) we don't forget to clear the routing information (i.e. we don't leave garbage behind).

      Affected versions: all versions since 5.0.

            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            0 Vote for this issue
            6 Start watching this issue