Skip expired historical chunk documents during authoritative collection metadata recovery

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2026-08-03, CAR Team 2026-08-17
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      A shard-local chunk document in config.shard.catalog.chunks is expired iff:

      • the chunk is not currently owned by this shard and
      • the timestamp of the transition from this shard is beyond the WT history window.

      Changes:

      1. Add an optional parameter to makeCollectionAndChunksAggregation. When set, append the filter inside the $lookup sub-pipeline.
      2. Behind a feature flag, capture the WT oldest timestamp and pass the bounds to makeCollectionAndChunksAggregation.

            Assignee:
            Tymoteusz Slepowronski (Inactive)
            Reporter:
            Tymoteusz Slepowronski (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: