[SERVER-41895] Split RecoveryUnit::commitUnitOfWork() procedure into storage engine-specific and non-specific stages Created: 24/Jun/19  Updated: 06/Dec/22

Status: Backlog
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: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-41894 Use the same registerChange logic for... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

Presently, commitUnitOfWork() implementations do both storage engine-specific and non-storage engine-specific commit procedures.

In order to cleanly separate out the generic commit procedures, we could consider separating commitUnitOfWork() into two functions, both called in succession wherever commitUnitOfWork() is presently called. One function would do commit work specific to the storage engine, and would be required for each storage engine to implement, and the other would do generic commit work, and would only be implemented at the RecoveryUnit level.


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