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

Execution Architecture Guide: Oplog Collection

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.7.0
    • None
    • Storage
    • None
    • Fully Compatible
    • Execution Team 2020-06-15, Execution Team 2020-06-29

    Description

      Rough starting outline:

      Oplog Collection
          Purpose
              (‘an operations log’, entry for every write op, repl uses it, rollback, recovery, etc.)
          Oplog Visibility
              Oplog ‘Holes’
                  (because parallel writes)
              Oplog Read Timestamp
                  (only used for forward cursors, backwards skips)
          Oplog Truncation
              (capped collection or WT oplog stones)
              (special timestamps we will not truncate with WT -- for which we delay truncation)
              (new min oplog time retention, helps not fall off of the oplog)
              (oplog durability considerations across nodes)
      

      Definitely feel free to alter the layout and file additional tickets split the work into more manageable units. Please add topics if you can think of any. This outline is meant only to be a starting point.

      A couple helpful links for markdown basics:
      https://www.markdowntutorial.com/
      https://gist.github.com/asabaylus/3071099
      https://markdownlivepreview.com/

      Attachments

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: