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

Use record store directly to read from oplog for replication

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • None
    • Replication, Storage
    • None
    • Storage Execution

    Description

      By using the record store directly we can avoid any locking issues and use a snapshot to return data at any time.

      We must be careful of operations which drop/recreate the oplog, like resync/compact/etc, since the record store pointer will have to be re-acquired once it becomes invalid.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-5729 Special-case concurrency model for oplog, make reads not block as much

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-20328 Allow secondary reads while applying oplog entries

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-24661 Secondary block reader a very long time when replay oplog

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              scotthernandez Scott Hernandez
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: