ShardRegistry should not remove RSM when a live shard still uses the same replica set name

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-13, CAR Team 2026-04-27
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The ShardRegistry::_lookup method was unconditionally calling ReplicaSetMonitor::remove() for removed shard IDs without checking whether the RS name was still in use by a newly-added shard, causing HostUnreachable errors.

            Assignee:
            Igor Praznik
            Reporter:
            Igor Praznik
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: