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

priority_takeover_one_node_higher_priority jstest needs longer stepDownGuard

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.17, 3.4.7, 3.5.6
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4, v3.2
    • Linked BF Score:
      0

      Description

      The test occasionally fails because the high priority node steps up before the low priority node is elected. We can increase the stepDownGuard in priority_takeover_one_node_higher_priority.js to 10 * electionTimeoutMillis, then explicitly end the stepdown period on the high priority node with replSetFreeze after the low priority node is elected to avoid the test taking longer.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: