[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: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
After 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. |
| Comments |
| Comment by Max Hirschhorn [ 07/Mar/18 ] |
|
This was done as part of the testing for retryable writes in MongoDB version 3.6. |