Escape CheckMetadataConsistency hook assertion from running in sharded clusters

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0, 8.2.3, 8.0.17, 8.2.4, 8.0.18
    • Affects Version/s: 8.3.0-rc0, 8.2.0
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.2, v8.0
    • CAR Team 2025-10-27, CAR Team 2025-11-10
    • 0
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      We call DiscoverTopology as a last step if checkMetadataConsistency fails with CommandNotFound as part of the background hook. Then, we assert that we are NOT running in a sharded cluster because checkMetadataConsistency should exist in that context.

      However, we do not throw the last exception — we simply log it. We should ignore all errors coming from DiscoverTopology but throw if we are running in a sharded cluster and found CommandNotFound.

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

              Created:
              Updated:
              Resolved: