Memory consumption by different engines used in Mongodb database in Red Hat Satellite 6

Solution Verified - Updated

Environment

  • Red Hat Satellite 6.5 and later

Issue

  • Memory consumption by different engines used in Mongodb database in Red Hat Satellite 6

Resolution

  • The mmapv1 engine of mongodb database was the old storage engine which is currently not supported.

  • mmapv1 engine uses all free memory on the machine as its cache. System resource monitors show that MongoDB uses a lot of memory, but its usage is dynamic.

  • The wiredTiger engine is the new storage engine used in mongodb database which is currently supported.

  • Sometimes, mongod consumes randomly high memory as the wiredTiger engine can consume up to half of all memory for its local cache.

  • We recommend limiting the wiredTiger max cache. This has been tested at limiting the cache to 20% of the Satellite's physical RAM with little to zero performance impact. To set this value, refer to the article

For more KB articles/solutions related to Red Hat Satellite 6.x MongoDB Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x MongoDB-related Issues

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.