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

stagger the launching of resmoke jobs

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.11
    • Component/s: Testing Infrastructure
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      TIG 18 (08/05/16)
    • Linked BF Score:
      0

      Description

      BF-2654 was a failure that I think was due to 16 jobs all starting at exactly the same time. The tests in that particular suite tend to all follow the same setup, so all jobs simultaneously put a huge load on the disk system as they all started. To avoid this issue, I think we should put a half-second (or full-second) delay between the launching of multiple jobs in resmoke.
      As we roll out more powerful instances with more CPU's, the potential for I/O overload grows.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              isabella.siu Isabella Siu (Inactive)
              Reporter:
              milkie Eric Milkie
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: