Add checkOplogs test to concurrency suite

XMLWordPrintableJSON

    • Server Tooling & Methods
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The call to the checkOplogs() function (SERVER-25376) was removed from the concurrency suite because it was causing timeouts in Evergreen due to scanning 1GB oplog after each FSM workload. We may want to only call the checkOplogs() function after running X workloads, or refactor the function to scan only to where we left off from the last call to avoid doing so much I/O on our test machines.

            Assignee:
            Backlog - Server Tooling and Methods (STM) (Inactive)
            Reporter:
            Jonathan Abrahams (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: