-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
In order to gain some extra coverage in cross-binary compatibility, set should_downgrade: true in multi-version kill primary test suites:
$ find buildscripts/resmokeconfig/matrix_suites/generated_suites/ | grep 'last_[lts\|continuous]' | grep kill buildscripts/resmokeconfig/matrix_suites/generated_suites/sharding_kill_primaries_jscore_passthrough_last_lts_new_old_old_new.yml buildscripts/resmokeconfig/matrix_suites/generated_suites/replica_sets_kill_primary_jscore_passthrough_last_lts_new_new_old.yml buildscripts/resmokeconfig/matrix_suites/generated_suites/sharding_kill_primaries_jscore_passthrough_last_continuous_new_old_old_new.yml buildscripts/resmokeconfig/matrix_suites/generated_suites/replica_sets_kill_primary_jscore_passthrough_last_lts_new_old_old.yml
The option is currently not enabled in any kill primary suite:
$ git grep should_downgrade buildscripts/resmokeconfig/ | grep kill | wc -l 0
NB: despite the not intuitive parameter name, setting should_downgrade: true will mean that binaries will be downgraded or upgraded, always switched upon kill. The assignee may decide changing the parameter name in order to make it clearer.
- depends on
-
SERVER-107168 Allow resmoke to restart mongod in different binary version after kill
-
- Needs Scheduling
-