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

Add checkOplogs test to concurrency suite

    XMLWordPrintable

    Details

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: