create upgrade guide for mongodb-2.6 (DOCS-2227)

[DOCS-2070] Add notes about 2.6 --upgrade on a sharded cluster Created: 10/Oct/13  Updated: 02/Nov/16  Resolved: 15/Nov/13

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: mongodb-2.6

Type: Sub-task Priority: Major - P3
Reporter: Randolph Tan Assignee: Zack Brown
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-8678 Implement automated config schema upg... Closed
Participants:
Days since reply: 10 years, 18 weeks, 6 days ago

 Description   

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.


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