[DOCS-1251] Instructions to upgrade sharded cluster to 2.4 are missing doc on required free disk space for config servers Created: 18/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 |
|
When upgrading a sharded cluster from 2.2 to 2.4, the config servers require considerable amounts of free space in order to successfully complete the upgrade. The documentation should state that the amount of free space on the filesystem where the config server db is stored should 4x-5x the amount of space currently used by the config DB data files. Checking for this free space should be part of the pre-upgrade checklist. |
| 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: |
| Comment by Kay Kim (Inactive) [ 18/Mar/13 ] |
|
Added as step 1: 1. Before you start the upgrade, ensure that the amount of free space on the filesystem for the config database is 4 to 5 times the amount of space currently used by the config database data files. |