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

Check for term equality when comparing OpTime for a writeConcern

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.1
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2019-10-21
    • 28

    Description

      haveNumNodesReachedOpTime and haveTaggedNodesReachedOpTime currently use OpTime comparison functions defined here. But if a OpTime with a higher term comes via heartbeat, we shouldn't consider that as a writeConcern satisfaction. So we should also check for term equality before waking up writeConcern waiters. If a higher term comes, it means that the node will be stepping down. And on member state changes after the stepDown, the existing logic should be able to wake up all remaining waiters with stepDown errors.

      Attachments

        Activity

          People

            lingzhi.deng@mongodb.com Lingzhi Deng
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: