Speed up accesses of oplogTruncateAfterPoint document

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The RecordId of the oplogTruncateAfterPoint document will never change during steady-state replication, but we constantly use the _id index to read and update the document. We could cache the RecordId to speed up reads and writes. Or we could cluster the collection, but that would need to consider possibly backward-breaking changes that would prevent downgrade.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: