[DOCS-847] need to doc upgrade of cluster from v2.2 to v2.4 format Created: 05/Dec/12  Updated: 06/Jan/13  Resolved: 06/Jan/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Critical - P2
Reporter: Greg Studer Assignee: Sam Kleinman (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates DOCS-929 Upgrade Procedure for 2.4 Config Serv... Closed
Participants:
Days since reply: 11 years, 6 weeks, 4 days ago

 Description   

As part of an upgrade of a cluster from v2.2 to v2.4, the config database will need to be upgraded and epochs added to all collections (to support SERVER-939). v2.2 is backwards-compatible with these changes, however v2.0 is not. In order to migrate the cluster, a single v2.4 mongos must be started with --upgrade, and no collection metadata changes (adding shards, dropping databases, dropping collections) can happen while the upgrade is in progress.

We need to doc this upgrade process for 2.3.2/2.4.



 Comments   
Comment by Sam Kleinman (Inactive) [ 06/Jan/13 ]

marking 847 as the duplicate as 929 has more information.

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