diff options
| author | Greg Studer <greg@10gen.com> | 2013-10-08 19:22:02 -0400 |
|---|---|---|
| committer | Greg Studer <greg@10gen.com> | 2013-10-09 10:15:16 -0400 |
| commit | f112796ee44768ff9a4d694600724203adf84bd1 (patch) | |
| tree | 03c232dab9f72cae792ba0ee23bd08bc71faf590 /jstests | |
| parent | f8a42a561a37d683234a383ccdae5721030560e1 (diff) | |
| download | mongo-f112796ee44768ff9a4d694600724203adf84bd1.tar.gz | |
SERVER-9660 use buildinfo instead of serverStatus in config upgrade
Diffstat (limited to 'jstests')
| -rw-r--r-- | jstests/multiVersion/upgrade_cluster_v3_to_v4.js | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/jstests/multiVersion/upgrade_cluster_v3_to_v4.js b/jstests/multiVersion/upgrade_cluster_v3_to_v4.js index 3431a8e735e..139aa83f1c2 100644 --- a/jstests/multiVersion/upgrade_cluster_v3_to_v4.js +++ b/jstests/multiVersion/upgrade_cluster_v3_to_v4.js @@ -127,6 +127,29 @@ createShardedCollection(mongos22.getDB("admin"), mongos22.getCollection("fooMixe st.printShardingStatus(); // +// Upgrade 2.0/2.2 cluster to all mongoses at 2.2 +// + +jsTest.log("Upgrading all mongoses to 2.2..."); + +st.upgradeCluster("2.2", { upgradeShards : false, upgradeMongos : true, upgradeConfigs : true }); +st.restartMongoses(); + +// +// Make sure 2.4 mongoses won't start in 2.0/2.2 shard cluster +// + +jsTest.log("Starting v2.4 mongos in 2.0/2.2 (shard) cluster....") + +var mongos = MongoRunner.runMongos({ binVersion : "2.4", configdb : configConnStr }) +assert.eq(null, mongos); + +var mongos = MongoRunner.runMongos({ binVersion : "2.4", configdb : configConnStr, upgrade : "" }) +assert.eq(null, mongos); + +jsTest.log("2.4 mongoses did not start or upgrade in 2.0/2.2 (shard) cluster (which is correct).") + +// // Upgrade 2.0/2.2 cluster to only 2.2 // |