Description of problem: Running the SCL mongodb image on OpenShift with an underlying physical server prints warnings related to NUMA and performance. 2017-09-07T16:25:00.984+0000 [initandlisten] ** WARNING: You are running on a NUMA machine. 2017-09-07T16:25:00.984+0000 [initandlisten] ** We suggest launching mongod like this to avoid performance problems: 2017-09-07T16:25:00.984+0000 [initandlisten] ** numactl --interleave=all mongod [other options] Version-Release number of selected component (if applicable): mongodb 3.2 How reproducible: Always. Steps to Reproduce: 1. Bring up a mongo container on a physical server with NUMA Actual results: Warnings and potential performance related issues. Expected results: A flag or option to start mongodb with numactl (assuming it's installed) as per the mongodb recommendations. Additional info:
Fix for this won't be enabled by default - it isn't applicable for s390x architecture and it is kind of performance tuning ~ it won't fit everybody. In rh-mongodb36 it will be possible to use numactl to launch mongodb server when using systemd service files. It can be done by editing /etc/sysconfig/mongod or /etc/sysconfig/mongos files - NUMACTL variable is used to launch mongod/mongos server. (upstream recommended value is provided in comment in sysconfig files) Are you requesting to change this in rh-mongodb32 or can I move this bug to rh-mongodb36 version and close it?
Configurable is great. Moving it to fix the next release is fine. Matt
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1281