Concurrent stepdown suites on 3.6 branch still use 5-second election timeout

XMLWordPrintableJSON

    • Server Tooling & Methods
    • ALL
    • 15
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The changes from 3aa3155 as part of SERVER-30642 were ineffective at increasing the election timeout for the concurrency_sharded_with_stepdowns*.yml test suites because the JavaScript version of the stepdown thread reconfigures the replica set and sets a 5 second election timeout by default. We should additionally additional set electionTimeoutMS=1 day as part of the stepdown options specified to the ContinuousStepdown.configure() function.

      Note: This is no longer an issue for the 4.0 or master branches because they've switched to using the Python version of the stepdown thread, which doesn't reconfigure the replica set.

              Assignee:
              Backlog - Server Tooling and Methods (STM) (Inactive)
              Reporter:
              Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: