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

Reduce noisiness in flow_control_replica_set.js

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.1, 4.3.1
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2
    • Sprint:
      Execution Team 2019-09-23
    • Linked BF Score:
      18

      Description

      The flow_control_replica_set.js test is intended to ensure that, when Flow Control assigns a certain number of tickets in a period of one second, an inserts-based workload executes approximately that number of inserts per second. However, the test is expected to be noisy in its current state, and can fail on a slow machine.
      To reduce false positive failures of the test, we should attempt to make it less subject to noise.

      One potential solution for this is to perform two calibration runs of the inserts workload. The first calibration run (already present in this test) determines an average rate of inserts without flow control. The second calibration run (to be added in this ticket) runs the same workload where flow control assigns a number of tickets that is equal to the ceiling of the calculated average of the first calibration run. If the rates of writes in both calibration runs are approximately equivalent, the test can proceed. Otherwise, the test run is deemed to be too noisy and it should return early.

      Another solution is to move this test into the serial_run suite, which only runs tests serially and therefore reduces the likelihood for noise. Given the comparative ease of this solution, we will pursue it.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              maria.vankeulen Maria van Keulen
              Reporter:
              maria.vankeulen Maria van Keulen
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: