[SERVER-24327] Run stepdowns in parallel with other tests using resmoke.py Created: 31/May/16  Updated: 07/Mar/18  Resolved: 07/Mar/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.3.6
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Resolution: Duplicate Votes: 0
Labels: tig-dataconsistency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-30979 Run the fuzzer with CSRS primary step... Closed
duplicates SERVER-31194 Add a version of retryable_writes_jsc... Closed
duplicates SERVER-31452 Run fuzzer with shard stepdowns Closed
Participants:

 Description   

After SERVER-24324 and SERVER-23226 are committed, we should write a JS file that triggers elections and run that file concurrently with a test suite as a separate resmoke.py job or testcase.

sharding_continuous_config_stepdowns.js can be used as a blueprint when implementing this.

The jstestfuzz_replication* suites can be used as guinea pigs for this feature, as they do not require commands to succeed or retry if they fail.

Running step downs concurrently with tests has found issues in the past, e.g. SERVER-17403.



 Comments   
Comment by Max Hirschhorn [ 07/Mar/18 ]

This was done as part of the testing for retryable writes in MongoDB version 3.6.

Generated at Thu Feb 08 04:06:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.