1:mongod logs have a lot of such errors:
[Initandlisten] Connection refused because too many open connections:
2: View System Limitations
Core file size (blocks,-c) 0data seg size (Kbytes,-D) unlimitedscheduling priority (-e) 0file size (blo Cks,-F) unlimitedpending signals (-I ) 256072max locked memory (Kbytes, L) 64max memory size (Kbytes,-m) UNL Imitedopen files (-N) 65535pipe size (bytes,-p) 8POSIX message Queues (bytes,-Q) 819200real-time Priori Ty (-r) 0stack size (Kbytes,-s) 10240cpu time (seconds,-t) Unlimitedmax user Processes (-u) 65535virtual Memory (Kbytes,-V) unlimitedfile locks (-X) Unlimited
It is not a system problem to verify the startup parameters of the mongod.conf.
3: Restart Mongod after adding numactl--interleave=all parameter
#numactl--interleave=all Mongod--config/mongodb/mongod.conf
4: You can also add the following parameters to temporarily change the memory management policy
#echo 0 >/proc/sys/vm/zone_reclaim_mode
#echo 2 >/proc/sys/vm/overcommit_memory
Next blog post:
Http://www.cnblogs.com/xiaoit/p/4484343.html
MongoDB NUMA series Issue One: [Initandlisten] Connection refused because too many open connections: