[DOCS-929] Upgrade Procedure for 2.4 Config Server Changes Created: 27/Dec/12  Updated: 15/Jan/13  Resolved: 10/Jan/13

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-2.4
Fix Version/s: mongodb-2.4

Type: Task Priority: Major - P3
Reporter: Greg Studer Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by DOCS-847 need to doc upgrade of cluster from v... Closed
Related
related to SERVER-7984 Infrastructure for config database up... Closed
Participants:
Days since reply: 11 years, 5 weeks, 5 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.

When an upgrade fails in the critical section when adding epochs to all collections in the config server, we print a message with a documentation link - this page needs to be created and maintained.

Needed pre-2.4.



 Comments   
Comment by auto [ 11/Jan/13 ]

Author:

{u'date': u'2013-01-10T23:19:50Z', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-929 edits to release notes for text search
Branch: master
https://github.com/mongodb/docs/commit/e8625759c9998ab833bc51ccc0043d2d8a256dfc

Comment by auto [ 11/Jan/13 ]

Author:

{u'date': u'2013-01-10T22:49:56Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-929: corrections to introduction from discussion with paul
Branch: master
https://github.com/mongodb/docs/commit/dc699fc9f31c97896e8ab2921c1668be899e07d4

Comment by auto [ 10/Jan/13 ]

Author:

{u'date': u'2013-01-10T23:07:30Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-929 upgrade procedure edits
Branch: master
https://github.com/mongodb/docs/commit/bec9c3f6a5bd239ff9510db0603184ef8786b69b

Comment by auto [ 10/Jan/13 ]

Author:

{u'date': u'2013-01-10T22:39:34Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-929: edits to release notes upgrade process
Branch: master
https://github.com/mongodb/docs/commit/206737a614f5273e46a3b143c7925f162ffeaefe

Comment by auto [ 10/Jan/13 ]

Author:

{u'date': u'2013-01-10T19:49:24Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: merge: DOCS-929
Branch: master
https://github.com/mongodb/docs/commit/8e721518700b2483db17d3f83b139ae450cf7631

Comment by auto [ 10/Jan/13 ]

Author:

{u'date': u'2013-01-10T15:01:03Z', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}

Message: DOCS-929 config server upgrade review edits
Branch: master
https://github.com/mongodb/docs/commit/4764b8a6184e897fb5cb048143f0ef2d96783aba

Comment by auto [ 10/Jan/13 ]

Author:

{u'date': u'2013-01-09T23:33:32Z', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}

Message: DOCS-929 config server upgrade (quick, early draft)
Branch: master
https://github.com/mongodb/docs/commit/55af6a49da8af71a222ceec3bf0186c15bd0caf2

Comment by auto [ 03/Jan/13 ]

Author:

{u'date': u'2013-01-03T23:49:12Z', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}

Message: DOCS-929 changed link to release notes for now
Branch: master
https://github.com/mongodb/mongo/commit/a428db77dfdebf04c4a7dcd4cc7073ec2160a463

Comment by Daniel Pasette (Inactive) [ 03/Jan/13 ]

This documentation needs to be prepared for 2.3.2 release.

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