Red Hat Bugzilla – Bug 1268258
mongodb fails to start with numa interleave policy on RHEL7.1
Last modified: 2017-08-11 08:30:25 EDT
Description of problem: mongodb recommends to interleave memory across all nodes for better performance. As part of this exercise, i tried to interleave mongodb and check satellite performance. Mongodb fails to start with NUMA interleave. http://docs.mongodb.org/manual/administration/production-notes/ 1) interleave across nodes for mongod: numactl --interleave=all /usr/bin/mongod -f /etc/mongodb.conf NUMA is interleaving across nodes as shown below. http://pastebin.test.redhat.com/316482 2) Start mongod. It fails to start. systemctl start mongod.service. Strace: http://pastebin.test.redhat.com/316531 Its an issue with systemd. 3) Added init.d script for mongod. Still fails to start. http://pastebin.test.redhat.com/317072 Without interleave, mongod starts successfully. Version-Release number of selected component (if applicable): mongodb-2.4.9-3.el7sat.x86_64 katello-2.2.0.16-1.el7sat.noarch pulp-server-2.6.0.15-1.el7sat.noarch How reproducible: Steps to Reproduce: 1. numactl --interleave=all /usr/bin/mongod -f /etc/mongodb.conf 2. systemctl start mongod.service Actual results: Mongod fails to start. Expected results: Mongod should start after numa interleave Additional info:
Ran mongodb with numa interleave on centos/ Not sure if this is the recommended one. http://psuriset.com/2015/12/20/starting-mongodb-on-centos-with-numa-disabled
Can you shed some light on what you believe the issue is? i.e. Do you believe it the issue is in the version of MongoDB we ship? The packaging around the MongoDB that we ship? An issue with systemd in general?
i believe its with mongodb we ship.
This bz has been moved to an upstream issue. We will no longer be tracking this in the downstream. When the upstream issue is fixed, the next release of Satellite will include the fix. If this is a concern, please reach out to Bryan Kearney or Rich Jerrido. Thank you.