[DOCS-2425] explicitly document that upgrading a replset from <2.4 to 2.6 should not be done Created: 17/Dec/13  Updated: 11/Jan/17  Resolved: 02/Jan/14

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

Type: Task Priority: Major - P3
Reporter: Michael O'Brien Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 10 years, 6 weeks, 6 days ago

 Description   

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

For standalone and replset cases, we don't explicitly state that upgrading from <=2.2 is unsupported. However, we probably should, and recommend that users first follow the upgrade process to reach 2.4 first. Upgrade paths from older versions are not tested so we shouldn't guarantee that they are expected to work.

(For the case of upgrading a sharded cluster there is a pretty stern warning.)



 Comments   
Comment by Githook User [ 02/Jan/14 ]

Author:

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

Message: DOCS-2425 clarify upgrade path to 2.6
Branch: master
https://github.com/mongodb/docs/commit/1b4c287241f45a73a64b65dc56589788e1c5d743

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