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

Relax implementation of getDatabaseWithRefresh/getCollectionRoutingInfoWithRefresh of the CatalogCache

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.0.0-rc0
    • Sharding
    • Fully Compatible
    • Sharding EMEA 2021-05-03, Sharding EMEA 2021-05-17
    • 165

    Description

      The goal of this ticket is to relax the implementation of the getDatabaseWithRefresh and the getCollectionRoutingInfoWithRefresh methods: both of them invalidate an entry in their caches.

      Instead of doing that, we could just advanceTimeInStore using a ComparableDatabaseVersion/ComparableChunkVersion with the forcedRefresh flag.

      Some tests, for instance this one, will have to be fixed.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-56469 The shard server catalog cache loader should replace the entries on config.cache.collections and not just update them

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-53861 Implement stop migrations procedure for DDL operations

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-55146 Bump collection version on any modification of config.collections reshardingFields or allowMigrations fields

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
              sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: