[SERVER-40642] Add upgrade/downgrade tests for split horizon Created: 15/Apr/19  Updated: 24/May/19  Resolved: 24/May/19

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: ADAM Martin (Inactive) Assignee: ADAM Martin (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Dev Tools 2019-05-06, Dev Tools 2019-05-20, Dev Tools 2019-06-03
Participants:

 Description   

Test that the horizons field in repl set cofig does not cause errors in startup (when supported). Graceful downgrade scenarios (when split horizon isn't used). Mixed version replica sets (some support it some don't) shouldn't have problems if split-horizon isn't used.



 Comments   
Comment by Max Hirschhorn [ 19/May/19 ]

Max Hirschhorn Do we have a way to run upgrade/downgrade tests against a specific point-release of an older version?

adam.martin, it is possible. You would want to update the invocation for the setup_multiversion_mongodb.py script to list the specific point-release of the 3.6 branch you want to test against. You would then specify binVersion='3.6.x' to MongoRunner/ReplSetTest/ShardingTest in a jstests/multiVersion/ test.

Comment by ADAM Martin (Inactive) [ 17/May/19 ]

max.hirschhorn Do we have a way to run upgrade/downgrade tests against a specific point-release of an older version? The upgrade/downgrade tests for split-horizon would require running against releases of 3.6 which do not have split-horizon support.

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