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

Create a formal storage interface for oplog collection

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Storage
    • None
    • Storage Execution
    • Execution Team 2019-07-01

    Description

      There is a great deal of specialized 'if (oplog) do this' logic in the WiredTigerRecordStore class. The WiredTigerKVEngine class has less, but still a significant amount of special handling.

      1. this makes it incredibly difficult to modify because we often do not document how a particularly part works, let alone how it all works together.
      2. currently we are only supporting transactions and some other replication features on the WT storage engine. We should formalize the support thereof if we wish to extend the features to other storage engines in the future, like Biggie, or truly continue to support a pluggable storage engine layer.
      3. We cannot unit test it as it is currently implemented.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated: