RefineCollectionShardKey doesn't need to store unowned chunks

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2026-04-13
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Once the ChunkMap is able to support a range of a shard key with gaps (SERVER-119607), we can improve refineCollectionShardKey so it doesn't persist unowned chunks to config.shard.catalog.chunks, and doesn't bulk-load all chunks into memory either.

            Assignee:
            Rustam Gusein-zade
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: