Raise election timeouts as a way to provide more stable replica set test topologies

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.5, 3.7.3
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v3.6
    • Repl 2018-01-29, Repl 2018-02-12, TIG 2018-03-12
    • 15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      For Javascript tests that aren't trying to directly test any aspect of the consensus machinery, we should consider making unwanted elections impossible, so as to cut down on the issue of spurious topology changes interfering with the actions a test is executing. Raising election timeouts to some very high value could be one solution to this. It would make tests more resilient to machine/network slowness, and improve their stability. Setting the priority of secondary nodes to 0 (in addition to high election timeouts) could also help reduce the triggering of unexpected election.

      We may want to consider reviewing tests and see which ones we consider "consensus agnostic", and those we do not.

            Assignee:
            Jonathan Abrahams (Inactive)
            Reporter:
            Will Schultz
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: