[SERVER-65702] upgradeCluster in multi_cluster.js incorrectly used to downgrade sharded clusters Created: 15/Apr/22  Updated: 29/Oct/23  Resolved: 03/May/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Jason Chan Assignee: Sanika Phanse (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2022-05-02, Sharding NYC 2022-05-16
Participants:

 Description   

Currently, we seem to use upgradeCluster to double as downgrade by passing in a downgraded version (example). However, our documented downgrade procedures indicate that the order in which we restart the binaries should be the reverse of the upgrade procedure:
For upgrade, we restart in order of config servers -> shards -> mongos
For downgrade, we restart in order of mongos -> shards -> config servers.

For this ticket, we should create a separate downgradeCluster helper and make sure each reference to upgradeCluster(downgradeVersion) is updated appropriately.



 Comments   
Comment by Githook User [ 02/May/22 ]

Author:

{'name': 'Sanika Phanse', 'email': 'sanika.phanse@mongodb.com', 'username': 'sphanse99'}

Message: SERVER-65702 upgradeCluster in multi_cluster.js incorrectly used to downgrade sharded clusters.
Branch: master
https://github.com/mongodb/mongo/commit/eea1c78a009e0d477a825674dbf41e83afa4970b

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