Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11494

Update storage engine notes in Cloud Manager backup preparations page is out of date

    XMLWordPrintable

    Details

    • # Replies:
      0
    • Last comment by Customer:
      true
    • Story Points:
      0.1
    • Sprint:
      KANBAN BUCKET

      Description

      Under Storage Engine, we currently say:

      If you do not specify a storage engine, Cloud Manager uses MMAPv1 by default.

      Cloud Manager's backup daemons use the default storage engine of the mongod unless told otherwise. For MongoDB 3.0, this is MMAPv1, but for 3.2+ it's WiredTiger. Also MongoDB 3.0 is past its end-of-life date, so we may want to update this part too?

      Note that this is also incorrect in the same Ops Manager docs.

      The MMAPv1 engine minimizes storage in the blockstore: all blocks are already compressed and padding is disabled. WiredTiger compression offers no further storage benefit.

      Please note that Cloud Manager uses S3 blockstores, not MongoDB blockstores, so I believe these two sentences can be removed from the Cloud Manager docs.

      Blockstores are still very common in Ops Manager. Even though we *strongly* recommend that no one run more than 1 mongod per server, customers still tend to co-locate their appdb nodes with their blockstore nodes. For this reason, we may want to mention in the Ops Manager docs that with WiredTiger they can tune the cache all the way down to fit more than 1 mongod per server, but they really can't do that safely with MMAPv1.

        Attachments

          Activity

            People

            • Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 47 weeks, 5 days ago