[DOCS-2920] Comment on db.upgradeCheck() and db.upgradeCheckAllDbs() Created: 17/Mar/14 Updated: 20/Mar/14 Resolved: 20/Mar/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.2, mongodb-2.6 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Linda Qin | 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, 47 weeks, 6 days ago | ||||||||
| Description |
|
http://docs.mongodb.org/master/reference/method/db.upgradeCheck/
|
| Comments |
| Comment by Githook User [ 20/Mar/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Matt Dannenberg [ 18/Mar/14 ] |
|
1. It does do collection scans and it is worth adding a warning about that. 2. I agree with what you've come up with. Turning off the balancer would be a good idea, but I believe it would just miss possible problems if you don't (it wouldn't explode or anything). We should probably have someone run it against the assorted configurations (sharded, replicaset) to ensure we haven't missed any blatant problems. |