[DOCS-4233] Add a warning to db.upgradeCheckAllDBs and db.upgradeCheck() that it may take a while to run Created: 24/Oct/14 Updated: 16/Mar/15 Resolved: 05/Nov/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.13 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Linda Qin | Assignee: | Sam Kleinman (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, 15 weeks ago | ||||
| Description |
|
Since these two upgrade checks perform collection scans to scan all the documents, it may take a while to complete the check if the data size is big. It would be nice to add this warning in the documents for these two commands, so that users can be aware of the time required to perform the upgrade check.
|
| Comments |
| Comment by Githook User [ 05/Nov/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |