Fast OplogStart mechanism for storage engines supporting arbitrary DiskLocs

XMLWordPrintableJSON

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

      This is an internal feature that storage engines can opt into. If they support storing arbitrary keys as the loc in an insert, they can use the "ts" field from oplog entries (using the provided methods to extract the key). This allows replication to ask the storage engine where to look when a secondary tries to fetch oplog entries using a query like {ts: {$gt: OpTime(123, 445)}}.

              Assignee:
              Mathias Stearn
              Reporter:
              Mathias Stearn
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: