Improve reliability of FSM tests for bulk operations

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • QE 2025-02-17, QE 2025-03-03, QE 2025-03-17, QE 2025-03-31
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      A recent investigation (SERVER-89708) highlighted a potential issue in fsm tests where bulk crud operations are performed.
      The investigation found that any crud operation that relies on bulk execution (as defined here) can potentially throw a NoProgressMade, especially under a heavy concurrent load (such as moveCollection)
      For SERVER-89708, which only targeted the timeseries_mixed_operation.js test, the solution was to wrap the insertions/deletions within a helper that loop retries until success. 

      Ideally, writing fsm tests should be easier.
      The goal of the ticket is to review crud operations in fsm tests and assess if a more generic solution can be found to retry in case of NoProgressMade

              Assignee:
              Kristina Znam
              Reporter:
              Enrico Golfieri
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: