[TEST ONLY] make check_metadata_consistency.js test resilient to CSRS stepdowns

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 7.0.0, 8.0.0, 8.2.0
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • ALL
    • 0
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-108800 fixed a direct write to the config server on the testUnexpectedAdminDatabaseInGlobalCatalog function in the check_metadata_consistency.js test by making it retryable. This was not enough to prevent failures though, because there are other writes in the jstest (i.e. in testMisplacedCollectionOnConfigServerhttps). The purpose of this ticket is to change all the direct writes to the config server and make them retryable, and review all possible config server operations and make them resilient to step downs.

            Assignee:
            Unassigned
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: