Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

The switch to the wiredTiger Storage Engine, offered has a great performance improvement has brought also a big memory issue: as reported in upstream documentation[0] the engine can consume up to half of all memory for its local cache.

[0] https://docs.mongodb.com/manual/core/wiredtiger/

In the solution is reported how to limit the cache size:

https://access.redhat.com/solutions/4505561

but that value is not tested. Customer are left with no reasonable/tested/reference value.

This situation leave customers with two bad options:
- the risk that OOM killer will stop Mongo in case of resources contention
- the risk to affect performance by choosing an arbitrary value for the cache size


Version-Release number of selected component (if applicable):
Sat 6.5+


Actual results:
No guidance on how to avoid mongo taking possession of a Sat6

Expected results:
Having guidance with documented values according to host numbers or other parameters, in a shape like https://github.com/RedHatSatellite/satellite-support/tree/master/tuning-profiles

*** This bug has been marked as a duplicate of bug 1798668 ***