-
Type: Sub-task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Server
-
Labels:None
It's pretty much the same with 2.4 with the following changes:
1. Turning off the balancer is not actually required, but we probably want to train our users to always do this during upgrades.
2. There are no actual changes other than the config.version document.
3. Mongos should be upgraded first (important!) before mongod. Order does not matter if the user can ensure that no collections will be dropped while upgrading all mongos to 2.6.
4. No 2.2 process can be in the cluster to run --upgrade. And no new processes older than 2.4 should join after the upgrade completes.
- related to
-
SERVER-8678 Implement automated config schema upgrade from v4 to v5
- Closed