Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-94979

Make CheckMetadataConsistency hook don't rely on the discovery topology helpers

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2024-10-28, CAR Team 2024-11-25
    • 1

      The CheckMetadataConsistency hook currently relies on the discovery topology helpers, which uses the isMaster command in the background, to determine if the fixture cluster is sharded. Only then does it run the checkMetadataConsistency command.

      Relying on the discovery topology and sending the isMaster command in the background to assess the fixture cluster's topology is not robust. This is due to various circumstances such as retriable errors, interruptions, unrelated network errors, etc., which have been added as acceptable retriable errors over time. See SERVER-85640, SERVER-82803, SERVER-94977, and SERVER-81340.

      I propose that we modify the CheckMetadataConsistency hook so that it no longer relies on the discovery topology helpers. This change aims to reduce the likelihood of new retriable errors causing new BFs, which have not yet been accepted by the hook.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: