Always log optime when replication fails to apply an operation

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • Repl 2026-01-19
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We don't ensure that the optime of the failing operation is logged, which can make remediation difficult during crash loops (where we need to find the exact oplog entry that is causing the crash). We should make sure that the optime is always logged, regardless of redaction.

            Assignee:
            Unassigned
            Reporter:
            Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: