Thanks - we're currently running Solr inside of RHEL virtual machines inside of 
VMware. Running "numactl --hardware" inside the VM shows the following:

available: 1 nodes (0)
node 0 size: 16139 MB
node 0 free: 364 MB
node distances:
node   0 
  0:  10

So there is only one node being shown.  So there is only one node and only one 
memory bank.  Am I correct in assuming that means NUMA can't be the issue?

My best guess as to what is going on relates to that big memory-mapped file 
Solr allocates. Our search index is about 60GB or so, much bigger than the 16GB 
RAM the operating system has to work with. Could it be that the swapping is due 
to the memory-mapped file in some way?


-----Original Message-----
From: Lan [mailto:dung....@gmail.com] 
Sent: Wednesday, March 26, 2014 12:45 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr 4.3.1 memory swapping

It could be related to NUMA.

Check out this article about it which has some fixes that worked for me.

http://blog.jcole.us/2010/09/28/mysql-swap-insanity-and-the-numa-architecture/





--
View this message in context: 
http://lucene.472066.n3.nabble.com/Solr-4-3-1-memory-swapping-tp4126641p4127191.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to