Remove redundant conditional check for oplog truncate marker creation

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • v8.0
    • Repl 2024-11-25
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As part of SERVER-91777, we added a check to this conditional to avoid creating oplog truncate markers in the event that we are restoring a node.

      When magic restore is merged into master from the feature branch, passing in both userWritesAllowed and magicRestore in the above conditional might be redundant as we disallow user writes in magic restore here.

            Assignee:
            Ali Mir
            Reporter:
            Clarisse Cheah
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: