[SERVER-27587] mongod.service does not disable NUMA Created: 05/Jan/17  Updated: 05/Dec/22  Resolved: 16/Nov/22

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: 3.4.1
Fix Version/s: 4.1 Desired

Type: Bug Priority: Minor - P4
Reporter: Jonas Gustavsson Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 1
Labels: sdp-backlog-purge
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Red Hat Enterprise Linux Server release 7.2 (Maipo)


Issue Links:
Related
related to SERVER-7268 Add numactl to upstart scripts Closed
related to SERVER-3574 add numactl to init scripts Closed
Assigned Teams:
Server Development Platform
Operating System: ALL
Steps To Reproduce:

Copy https://github.com/mongodb/mongo/blob/master/rpm/mongod.service to /etc/systemd/system/mongod.service

Reload systemctl
systemctl daemon-reload

Starting MongoDB with:
systemctl start mongod

The warning about NUMA is displayed:
---------------------------------------------------------------------------

    • WARNING: You are running on a NUMA machine.
    • We suggest launching mongod like this to avoid performance problems:
    • numactl --interleave=all mongod [other options]
      ---------------------------------------------------------------------------
Participants:
Case:

 Description   

mongod.service does take NUMA into account as mongod.init does (SERVER-3574)



 Comments   
Comment by Iryna Zhuravlova [ 16/Nov/22 ]

After a careful backlog refinement, the team decided to close this ticket because of its low priority and limited resource capacity. If you believe that this ticket requires additional attention from the team and should be re-opened, feel free to change the status to "Needs Scheduling" and ping me or @alexander.neben

Generated at Thu Feb 08 04:15:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.