[SERVER-26466] Add checkOplogs test to concurrency suite Created: 05/Oct/16  Updated: 04/Dec/23  Resolved: 11/May/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: open_todo_in_code, stm, tig-concurrency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-48092 Complete TODO listed in SERVER-26466 Backlog
is related to SERVER-25376 Add a hook to check that oplogs in a ... Closed
Assigned Teams:
Server Tooling & Methods
Participants:

 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.



 Comments   
Comment by Etienne Petrel [ 04/Dec/23 ]

Hi, this is closed but there is still a reference here.

Comment by Ryan Timmons [ 11/May/20 ]

Closing as wont-fix to indicate that there is currently no intention of doing this. Please re-open if there is priority for this.

Generated at Thu Feb 08 04:12:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.