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

Generalize the WiredTigerRecordStore::OplogStones and move it out of WiredTigerRecordStore

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Storage Execution
    • Fully Compatible
    • Execution Team 2023-02-20, Execution Team 2023-03-06
    • 20

      After SERVER-45847 and SERVER-46869, we should be able to do this. The interface for WiredTigerRecordStore::OplogStones is already segregated into wiredtiger_record_store_oplog_stones.h.

      WiredTigerRecordStore::OplogStones holds a private WiredTigerRecordStore* for the oplog collection, but I think this should be able to be refactored out, switching it with accessing the record store via the oplog collection object, the usual way logic above the storage engine does.

      Extricating the _oplogStones object from the rest of the WiredTigerRecordStore, with special behavior in nooks and crannies, will be the tricky and uncertain part for this task.

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: