[DOCS-1161] clarify upgrade process details for 2.2 to 2.4 Created: 25/Feb/13 Updated: 04/Mar/13 Resolved: 04/Mar/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | mongodb-2.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael O'Brien | Assignee: | Sam Kleinman (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, 50 weeks, 2 days ago |
| Description |
|
release notes for upgrade 2.2 to 2.4 talk about the process of running mongos --upgrade, however it doesn't have detail on how to complete the upgrade after that. specifically, what order do you need to upgrade the other components (mongos, then configs, then shards, etc). |
| Comments |
| Comment by auto [ 04/Mar/13 ] |
|
Author: {u'date': u'2013-03-04T19:44:34Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |