Add concurrency_with_mongot_extension suites running FSM workloads against the mongot-extension

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • 9.0 Required
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Overview

      Restore the {{concurrency_with_mongot_extension_

      {single\_node,mongos,sharded\_collections}

      }} FSM suites (removed in SERVER-123445) running jstests/concurrency/mongot_fsm_workloads against the real mongot-extension.

      Split out of the with_mongot_extension e2e work (SERVER-129943 / SERVER-130648): the sole current workload, vector_search_ifr_toggle.js, toggles featureFlagVectorSearchExtension via IFR and requires the extension loaded, so these suites cannot ship in the legacy-clone phase and were deferred to land after the e2e extension enablement.

      Work

      * Add the three suite YAMLs (standalone, no base suite exists for the FSM corpus), loading only the mongot extension with featureFlagVectorSearchExtension + featureFlagExtensionsInsideHybridSearch enabled.
      * Add the three evergreen tasks (tag mongot_e2e_tests, resmoke_jobs_max: 1) with the same --disableFeatureFlags treatment as the e2e tasks.
      * Triage vector_search_ifr_toggle.js on sharded topologies -- it failed there (passed single-node) in earlier patch runs on SERVER-129943; see PR 57343's patch history.

            Assignee:
            Santiago Roche
            Reporter:
            Will Buerger
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: