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

Proactively evict cached entries after drop database/collection

    • Fully Compatible
    • v5.0
    • Sharding EMEA 2021-06-14, Sharding EMEA 2021-06-28

      Both drop database and drop collection on sharded cluster currently only invalidate the information on the DatabaseShardingState and the CollectionShardingRuntime after the database/collection have been dropped. The rename collection operation also cleans up the CollectionShardingRuntime.

      This is enough to ensure that subsequent requests will be causal consistent with the DDL operation.

      In order to free-up some memory, we should also proactively evict the cached entries for the dropped db/coll or renamed coll in the catalog cache.

            Assignee:
            simon.gratzer@mongodb.com Simon Gratzer (Inactive)
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: