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

Log the oplog entry when we throw OplogOutOfOrder

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0, 8.1.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • v8.1, v8.0, v7.0, v6.0
    • Repl 2025-03-17, Repl 2025-04-14
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In the oplog applier we have this fassert that throws if we are attempting to apply an entry that is behind our current optime. We should considering adding logging here to show the contents of the entry, having more diagnostics here could be helpful in the future

            Assignee:
            sean.zimmerman@mongodb.com Sean Zimmerman
            Reporter:
            sean.zimmerman@mongodb.com Sean Zimmerman
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: