Fix failpoint usage in tests for multi-router test suits

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • Fully Compatible
    • ALL
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-117145 introduces multi-router support to sharding test suites. However, failpoints are defined in individual processes, meaning that their values need to be manually updated across all mongos instances in the cluster (as well as mongod instances). Without this, there is a risk of inconsistent behavior, as commands could be processed by different mongos routers with different failpoint settings.

      To address this, we need to implement a function that sets the failpoint value on all mongos and mongod instances in the cluster. The query optimization tests that modify the QO failpoints (disablePipelineOptimization and disableMatchExpressionOptimization) should be updated to use this new function.

      Useful links:

            Assignee:
            Kartal Kaan Bozdogan
            Reporter:
            Alexander Ignatyev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: