[SERVER-41894] Use the same registerChange logic for ephemeralForTest as other storage engines Created: 24/Jun/19  Updated: 06/Dec/22  Resolved: 08/Jun/20

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

Type: Improvement Priority: Major - P3
Reporter: Maria van Keulen Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: intern_ephemeral_for_test
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-41895 Split RecoveryUnit::commitUnitOfWork(... Backlog
Assigned Teams:
Storage Execution
Participants:

 Description   

SERVER-18867 no longer requires individual storage engines to implement their own registerChange logic by moving this logic up to the RecoveryUnit class. The ephemeralForTest storage engine must still implement its own registerChange logic because the generic RecoveryUnit registerChange logic added as of SERVER-18867 has an invariant that fails on ephemeralForTest.

ephemeralForTest should be modified to use the generic RecoveryUnit registerChange logic.



 Comments   
Comment by Gregory Wlodarek [ 20/May/20 ]

We should be able to close this after PM-1244

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