Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-84481

Explicitly use RecoveryUnitNoop for storage engine initialisation

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • CAR Team 2024-01-08, CAR Team 2024-01-22

      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.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: