Decide if catalog shards need ShardServerCatalogCacheLoader

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding NYC
    • Fully Compatible
    • Sharding NYC 2023-02-06, Sharding NYC 2023-02-20
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The purpose of the ShardServerCatalogCacheLoader (SSCCL) is to cache config server collection metadata in locally replicated collections. When a config server acts as a shard, it will already replicate the real metadata collections, so in theory using the SSCCL isn't necessary. There may be some work to ensure no shard components rely on side-effects of the SSCCL, but this may be less work than deciding how to handle the SSCCL when transitioning in and out of dedicated config server mode and prevents storing metadata twice on catalog shards.

      Currently, catalog shards use the ConfigServerCatalogCacheLoader, but we should further investigate and make a final decision.

            Assignee:
            Jack Mulrow
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: