[DOCS-1244] Instructions to upgrade a sharded cluster are missing critical restrictions Created: 16/Mar/13 Updated: 19/Mar/13 Resolved: 18/Mar/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | William Zola | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
http://docs.mongodb.org/manual/release-notes/2.4-upgrade/#sharded-cluster-upgrade-procedure |
||
| Participants: | |
| Days since reply: | 10 years, 48 weeks, 2 days ago |
| Description |
|
The upgrade instructions should indicate that users should not run either sh.shardDatabase() or sh.shardCollection() (or the command equivalents) while the upgrade is taking place. The upgrade was not designed to run while those commands are taking place, and the result could potentially be a failed or corrupt upgrade. |
| Comments |
| Comment by auto [ 18/Mar/13 ] |
|
Author: {u'date': u'2013-03-18T22:39:40Z', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |