Use record store directly to read from oplog for replication

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: