[SERVER-44456] Create a WiredTigerOplogManager unit test or remove it completely Created: 06/Nov/19  Updated: 27/Oct/23  Resolved: 09/Dec/19

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

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Eric Milkie
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Execution Team 2019-12-16
Participants:

 Description   

It's hard to unit test changes to the oplog manager because no unit test has been set up. There appears to be a couple relevant unit tests hanging out in wiredtiger_record_store_test.cpp, which should be moved into a oplog manager unit test. The unit test setup might be similar to the wiredtiger_kv_engine_test.cpp unit test.



 Comments   
Comment by Eric Milkie [ 09/Dec/19 ]

Resolving in favor of SERVER-45025

Comment by Eric Milkie [ 07/Nov/19 ]

I changed the title to have this ticket consider removing the Manager completely instead of writing a test for it – we should do one or the other.

Comment by Dianna Hohensee (Inactive) [ 07/Nov/19 ]

Though this may want to await the completion of the Replicate Before Journaling project, as the OplogManager might be moved to a higher code level.

Generated at Thu Feb 08 05:06:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.