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

configTerm in memberData can regress on heartbeat response

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • Fully Compatible
    • ALL
    • Repl 2024-08-05
    • 0

      We cannot guarantee that heartbeats always come back in the order they are sent. It is possible that a node responded two heartbeats at configTerm 1 and 2, but the heartbeat with configTerm 1 arrived at the receiver at a later point. When we process the heartbeat response and update member data, we are not checking if the configTerm from heartbeat is greater than the current one, which could cause a configTerm regression for certain node and lead to cases like BF-33998.

            Assignee:
            huayu.ouyang@mongodb.com Huayu Ouyang
            Reporter:
            jiawei.yang@mongodb.com Jiawei Yang
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: