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

A slow thread in forceShardFilteringMetadataRefresh can reset the shard's filtering metadata to UNSHARDED

    • Sharding EMEA
    • Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03

      A shard refreshes its filtering metadata by first refreshing its CatalogCache, then using the fresh routing info from its CatalogCache to populate its filtering metadata.

      There areĀ checks to ensure a shard does not overwrite newer routing info for a sharded collection with older routing info, but there is no such check (and there can't be by design) to prevent the shard from overwriting routing info for a sharded collection with unsharded routing info.

            Assignee:
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: