[DOCS-6350] Add warning about changing wiredTigerCacheSizeGB Created: 09/Oct/15 Updated: 11/Jan/17 Resolved: 12/Apr/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | 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: | 8 years, 15 weeks, 6 days ago | ||||
| Description |
|
We encounter customers who hit out-of-memory conditions because they have increased the WiredTiger cache setting from its default of (about) half of physical memory. We should add a warning about this to our docs including production notes where we document this parameter (both command line and config file). |
| Comments |
| Comment by Githook User [ 29/Oct/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message:
|