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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor - P4 Minor - P4
    • None
    • 3.2.0
    • Replication
    • Replication
    • ALL
    • 0

    Description

      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.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: