[DOCS-5860] Comment on: "mms/tutorial/prepare-backing-mongodb-instances.txt" Created: 16/Jul/15  Updated: 07/Oct/15  Resolved: 07/Oct/15

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andrew Davidson Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.opsmanager.mongodb.com/v1.8/tutorial/prepare-backing-mongodb-instances/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.152 Safari/537.36
Screen Resolution: 1440 x 900
repo: REPONAME
source: tutorial/prepare-backing-mongodb-instances


Issue Links:
Related
related to DOCS-6335 Amended Ops Manger Application Databa... Closed
Participants:
Days since reply: 8 years, 24 weeks ago

 Description   

This is now superseded by a different request: https://jira.mongodb.org/browse/DOCS-6335



 Comments   
Comment by Bob Grabar [ 02/Sep/15 ]

Re #5:

  • Do we want to mandate MMAPv1 for the App DB?
  • Are there other differences in best practices for the two DBs?
Comment by Jon Rangel (Inactive) [ 01/Sep/15 ]

5. Provide separate best practice recommendations for the App DB vs. Blockstore DB, if applicable (e.g. mandate MMAPv1 for the APP DB, WT/MMAPv1 for Blockstore DB?)

Comment by Richard Kreuter (Inactive) [ 01/Sep/15 ]

I'd like to request the following changes:

  1. change the wording to indicate that mmapv1 is a best practice, not a strict requirement.
  2. perhaps give some context as to the nature of the suggestion (performance)
  3. perhaps indicate the MongoDB version to which this recommendation applies (3.0)
  4. please plan to revisit this issue some time after 3.2.0 is released, in case the recommendation needs to be altered.

See also:

https://wiki.mongodb.com/pages/viewpage.action?pageId=82609524

Generated at Thu Feb 08 07:51:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.