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

update tags.js to make nodes at indexes 3 and 4 unelectable

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.7, 3.5.10
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • Repl 2017-07-10
    • 0

      In tags.js, during some of the write concern tests, it is possible for the previously isolated node 4 to stand for election (see test case "partitions: [0-1-2] [1-4] [3-4]"), causing an unintended change in primary status. Setting the priority of one of the connected nodes to 4 will help to prevent an unexpected election from happening.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: