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

check_metadata_consistency.js should use retriable writes when contacting config server

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.1, 7.3.0-rc0, 7.0.5
    • Affects Version/s: 7.1.0, 7.2.1
    • Component/s: None
    • Labels:
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v7.2, v7.0
    • CAR Team 2023-12-11
    • 5
    • 1

      change_metadata_consistency.js often attempts to access to the config server for inserts or updates in order to force an inconsistency and make sure those would be check by the

      { checkMetadataConsistency ... }


      The test seems to access through direct connections to the CSRS in several points such here or here

      This can be problematic in case of a stepdown suite, where the insert/update would fail without being retried.

      The goal of this ticket is either to:

      • fix all the direct connection with the config server
      • ban the test from stepdown suites

      Evaluate if point 2 still make sense. The goal of this jstest seems be the idea of catching some forced inconsistencies and not to simulate a possible user scenario.

            pol.pinol@mongodb.com Pol Pinol
            enrico.golfieri@mongodb.com Enrico Golfieri
            0 Vote for this issue
            3 Start watching this issue