Update getDatabasesForShard to handle mixed shardID/uuid state

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2026-06-08, CAR Team 2026-06-22
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      During FCV upgrade/downgrade, routing information and even the metadata collections can contain a mix of shardIds and shardUUIDs. We need to evaluate all aggregations which use shardIds to see if they need to be updated to work via either reference.

      This is the first ticket in this stream of work and is responsible for evaluating the usages of getDatabaseForShard to see if it needs to be updated to handle mixed scenarios and (if so) update it to do so.

            Assignee:
            Josef Ahmad
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: