[DOCS-2685] v2.4 upgrade documentation not consistent about mixed versions Created: 06/Feb/14 Updated: 19/Feb/14 Resolved: 10/Feb/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.1 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint-slipstream | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 1 week, 2 days ago | ||||
| Description |
|
What is the intent of the following sentence in the upgrade notes for v2.4?
It's not obviously consistent with the instructions that the cluster should be upgraded in a particular order (mongos, config servers, shard members). If the note is only supposed to be about what's safe to downgrade (it's physically below a heading about downgrading), and is saying that the cluster may be downgraded in any order, or something to that effect, please clarify. http://docs.mongodb.org/manual/release-notes/2.4-upgrade/ |
| Comments |
| Comment by Githook User [ 10/Feb/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 10/Feb/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Richard Kreuter (Inactive) [ 06/Feb/14 ] |
|
Customer cited the offending line in defense of their having upgraded shards first, before mongos and config servers. |