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

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

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.7, 3.5.10
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Completed:
    • Sprint:
      Repl 2017-07-10
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: