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

Make secondaries refresh their database metadata from the persisted database cache

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.7.1
    • 3.7.4
    • Sharding
    • Fully Compatible
    • Sharding 2018-03-12, Sharding 2018-04-09

    Description

      We can do this by creating a 'config.cache.databases' collection on shards, and persisting the databaseVersion in it.

      We also need to persist a 'refreshing' flag into the entry in 'config.cache.databases' when starting a refresh, and a 'refreshing=false' and 'lastDatabaseVersionRefreshed=<DatabaseVersion' flags on completing the refresh, and add OpObservers so that the secondary will invalidate its in-memory cache entry for the database.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. SERVER-34145 Persist DB version on primary

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Task - A task that needs to be done. SERVER-33252 [passthrough testing] extend cluster catalog consistency hook to add checks for databaseVersion

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

          Task - A task that needs to be done. SERVER-43439 Make movePrimary wait for updates from the database refresh to be written before clearing the flag in the minOpTimeRecovery document

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

          Activity

            People

              janna.golden@mongodb.com Janna Golden
              randolph@mongodb.com Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: