[DOCS-7584] Refer to cacheSizeGB for Ops Manager 2.0 Test installation with backups Created: 06/Apr/16 Updated: 14/Mar/17 Resolved: 10/Mar/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Roger McCoy (Inactive) | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Done | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 8 weeks, 2 days ago |
| Epic Link: | C/OM Backup |
| Story Points: | 0.2 |
| Description |
|
In the Ops Manager Test installation document: The default 3.2 database will use WiredTiger. If installing a second mongod instance on the same host for the optional Backup Database, it would be helpful to mention setting a reduced size for cacheSizeGB to avoid resource issues in the test installation. Possibly could refer to this document. |
| Comments |
| Comment by Justin LaBreck [ 19/Dec/16 ] |
|
Hey all, I chatted with emily.hall about this issue. We recommend running multiple instances to customers often (app data/backup data) but don't mention memory contention anywhere. This is important since customers utilize this page for reference when creating production notes. I've been asked to re-open but I don't have that option. Should I create a new ticket? |