[SERVER-7969] NUMA Created: 18/Dec/12  Updated: 11/Jul/16  Resolved: 07/Jan/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: Dmitry Saratsky Assignee: James Wahlin
Resolution: Done Votes: 0
Labels: nh-240
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File mongod    
Participants:

 Description   

Hi,

please take a look on:
http://www.mongodb.org/display/DOCS/NUMA

Is it good to implement the above on our mongoDB servers (Amazon EC2 EBS Based m2.4xlarge instances) from you point of view?

Thanks,
Dima.



 Comments   
Comment by Dmitry Saratsky [ 07/Jan/13 ]

Hi,

sorry for long delay...
somehow missed your previous update.

Thanks for your help.
You can close this ticket

Dima.

Comment by James Wahlin [ 07/Jan/13 ]

Hi Dima,

One thing to note is on EC2 when you start mongod it will check numa settings and will issue a warning if action is needed on your part to change settings.

Let me know if you need further help with this.

Thanks,
James

Comment by James Wahlin [ 18/Dec/12 ]

Attached /etc/init.d/mongod script

Comment by James Wahlin [ 18/Dec/12 ]

Hi Dima,

If running Linux on numa hardware it is a good idea to disable. Are you running mongod via the /etc/init.d/mongod script? If yes and you are on 2.2 there are likely checks in place already that disable if on numa.

Check your start script for a reference to NUMA. If not present or if you have a custom start script you can see the attached mongod script for reference on how to disable.

Thanks,
James

Generated at Thu Feb 08 03:16:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.