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

Check the returned OpTime by multiApply() in 3.2 initial sync

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 3.2.0
    • Component/s: Replication
    • Replication
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      multiApply() may return null optime during shutdown after SERVER-21868. Null optime will hit an invariant in setMyLastAppliedOpTime(). We should check optime before setting my last applied optime.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: