[SERVER-84481] Explicitly use RecoveryUnitNoop for storage engine initialisation Created: 02/Jan/24  Updated: 11/Jan/24  Resolved: 11/Jan/24

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

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-77213 Move the all transactions-related sta... Backlog
Backwards Compatibility: Fully Compatible
Sprint: CAR Team 2024-01-08, CAR Team 2024-01-22
Participants:

 Description   

Currently, there is a dependency of ServiceContext on RecoveryUnitNoop where any OperationContext is first created with a RecoveryUnitNoop and then when the TransactionResources initialisation runs, gets populated with a real RecoveryUnit. This is unnecessary at the very least, but also it causes layering violation where a low layer such as ServiceContext reaches up into the storage engine.



 Comments   
Comment by Githook User [ 10/Jan/24 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-84481 Explicitly use RecoveryUnitNoop for storage engine initialisation

GitOrigin-RevId: 5c7e48c62e0ca2278db00ab803abd9a859eb06bf
Branch: master
https://github.com/mongodb/mongo/commit/46e193d4cf484fd1fe0431de21063ce7a4cdb959

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