add_remove_shard hook not resilient to kill primaries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2025-10-13
    • 0
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      The add_remove_shard.py hook decommissions the removed shard, and during that we forcefully drop databases on the primary of the given (former) shard. If the terminate_kill_primary hook runs concurrently it might happen that during the decommission steps the primary is not primaring anymore, so the cached connection is not valid anymore.

            Assignee:
            Wolfee Farkas
            Reporter:
            Wolfee Farkas
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: