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

Remove redundant conditional check for oplog truncate marker creation

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

      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:
            Unassigned Unassigned
            Reporter:
            clarisse.cheah@mongodb.com Clarisse Cheah
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: