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

Do not update term in protocol version 0

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.2.0-rc1
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl B (10/30/15)
    • 0

    Description

      I'm able to reproduce this bug by introducing a delay after the check of protocol version but before the schedule of updateTerm several lines later, so that term will be updated after the pv=0 reconfig in executor. As a result, the primary steps down because of the PV1 term in getMore request, even though it's in PV0. The time window of this bug is only several lines of code, but it did happen on Evergreen.

      Attachments

        Activity

          People

            siyuan.zhou@mongodb.com Siyuan Zhou
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: