[DOCS-4399] Mention storage engine changes during rolling upgrade in release notes Created: 20/Nov/14 Updated: 16/Mar/15 Resolved: 15/Dec/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.15, mongodb-3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 9 weeks ago | ||||
| Description |
|
In this section, http://docs.mongodb.org/manual/release-notes/2.8-upgrade/#upgrade-a-replica-set-to-2-8, we should mention that you can change the storage engine options to upgrade a replica set. We should be sure to mention that it will require a full-resync as the node comes back online. Perhaps we should also suggest a 2-phase upgrade process where first one upgrades the binary and then in the second phase changes the storage engine in a rolling fashion. |
| Comments |
| Comment by Githook User [ 17/Dec/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |