StaleConfig failure in $lookup when foreign collection is dropped and recreated on a different shard

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2026-04-27
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When using authoritative shard collection metadata (featureFlagShardAuthoritativeCollMetadata), a $lookup that gets pushed down to a shard can hit an unrecoverable StaleConfig error if the foreign collection was dropped and recreated on a different shard.

      The shard should recover from the stale CSR state and either re-route or refresh correctly, rather than looping to exhaustion.

            Assignee:
            Pol Pinol
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: