Escape CheckMetadataConsistency hook assertion from running in sharded clusters

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 8.3.0-rc0, 8.2.0
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2025-10-27
    • 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 running in a sharded cluster to prevent developers from adding this background hook in inappropriate contexts, such as replica set suites.

      However, we do not throw the last exception — we simply log it. We should ignore all errors coming from DiscoverTopology, but still perform the assertion to ensure the hook is not run in non-sharded clusters.

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

              Created:
              Updated: