[DOCS-2924] Document the downgrade steps for a sharded cluster Created: 17/Mar/14  Updated: 20/Mar/14  Resolved: 20/Mar/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.2

Type: Task Priority: Major - P3
Reporter: Linda Qin Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 9 years, 47 weeks, 6 days ago

 Description   

http://docs.mongodb.org/master/release-notes/2.6-upgrade

Apart from downgrading Authentication model, Text index and 2dsphere index, the downgrade order should be opposite with the upgrade order, so it should be:

  • Downgrade each shard using rolling downgrade.
  • Downgrade the config servers. The first config server in the mongos --configdb argument should be downgraded last.
  • Downgrade the mongos. It looks like there is no metadata change from v4 to v5, so the downgrade should be just a binary drop-in replacement.

It would be nice if we can document these steps.



 Comments   
Comment by Githook User [ 20/Mar/14 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2924 additional downgrade procedures
Branch: master
https://github.com/mongodb/docs/commit/bf2a866f1238b17e9f54245492cced23f3ce917f

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