[SERVER-49685] Restore ReplicationConsistencyMarkers test that set min valid without waiting for the changes to be durable Created: 17/Jul/20  Updated: 29/Oct/23  Resolved: 02/May/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Henrik Edin Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: EFT
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-05-16
Participants:
Linked BF Score: 64

 Description   

The test used to swap out the RecoveryUnit which is more difficult with the new ephemeralForTest engine as we need access to the KVEngine.



 Comments   
Comment by Githook User [ 02/May/22 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-49685 Re-enable test case in `ReplicationConsistencyMarkers` that min valid can be set without waiting for the changes to be durable
Branch: master
https://github.com/mongodb/mongo/commit/4b658b3f50340038f47c9fba66d3542a33ec9acc

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