Change the shard version update procedure of the migration source manager

XMLWordPrintableJSON

    • Fully Compatible
    • Sharding 2020-05-18, Sharding 2020-06-01, Sharding 2020-06-15, Sharding 2020-06-29
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As part of SERVER-47987 the way the cache is refreshed will be changed on a more optimized and safe way using a new scoped object. All this work will end on the removal of forceShardFilteringMetadataRefresh, which will make the local cache of a shard consistent with the config server. As part of this process the migration source manager needs to set the filtering metadata within the critical section, and should ensure:

      1. If the operation fails, it must set the collection metadata to unknown, so the real shard version can be recovered lazily when needed.
      2. There must not be any unnecessary refresh of the metadata after committing the new shard version, it should simply set the new shard version.
      3. There must not be any recovery.

            Assignee:
            Marcos José Grillo Ramirez
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: