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

Race condition in replsetprio1.js when initiating replset with nodes having different priorities

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.11, 5.0.5, 5.1.1, 5.2.0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v5.1, v5.0, v4.4
    • Sprint:
      Repl 2021-11-01
    • Linked BF Score:
      45

      Description

      replsetprio1.js has a race condition when initiating the replset. The nodes are initially configured with different priorities, and when initiating the replset, we add one node at a time by calling replsetReconfig. When adding the third node, there could be a concurrent priority takeover that causes primary node to stepdown and  failing replsetReconfig command to fail. As a result, the replset initiation process fails.

        Attachments

          Activity

            People

            Assignee:
            wenbin.zhu Wenbin Zhu
            Reporter:
            wenbin.zhu Wenbin Zhu
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: