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

Add a way to query the oplog past the lastApplied

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication

      Until we finish SERVER-88510, it won't be possible for chaining secondaries to read past the lastApplied opTime. However it would be nice if we can add a backdoor option for engineers to use when they're debugging so that they can see all oplog entries that have been written.

      For example, today on a two-node replica set if I stop secondary oplog application through the pauseBatchApplicationBeforeCompletion failpoint, I can continue to insert documents on the primary. However when I try to read oplog entries on the secondary I won't be able to see anything past the lastApplied, which was updated before the pauseBatchApplicationBeforeCompletion failpoint was set.

            Assignee:
            Unassigned Unassigned
            Reporter:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: