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

Fixing the ShardServerCatalogCacheLoader behavior when handling an update metadata format task

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Sharding 2021-02-22
    • 0

    Description

      The goal of this ticket is to fix 3 minor issues introduced when working on SERVER-53104:

      • Do not assume that after an update metadata format task we will always have a common task that updates some chunks. This is only true if the Chunks we got from the Config Server are more recent than the ones we have locally.
      • I found another minor bug when we compute the enqueued metadata CollAndChangedChunks: at this point we shouldn't set the flag to false but propagate whatever value we have in task.updateMetadataFormat.
      • Finally, when we are patching-up (i.e. adding/removing the timestamp) the results that are going to be sent back to the CatalogCache, we need to first update the Collection Info and then patch-up the ChangedChunks, but we are doing it the other way around.

      Attachments

        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: