Hello all, we have a SolrCloud implementation in production, with two servers running Solr 4.3.1 in a SolrCloud configuration. Our search index is about 70-80GB in size. The trouble is that after several days of uptime, we will suddenly have periods where the operating system Solr is running in starts swapping heavily. This gets progressively worse until the swapping slows things down so much that Zookeeper thinks the nodes are no longer available. If both nodes are swapping, it can lead to an outage, which has happened to us a couple of times.
My question is why is it swapping? Here's an example with numbers from our prod environment: - Total physical memory: 16GB - Physical memory usage: 15.58GB (99.4%) - Total swap space: 4GB - Swap space usage: 1.51GB (37.7%) - Total JVM Memory: 10GB - JVM heap: 1.89GB/4.44GB The "top" command reports that the JVM has 3.8GB resident RAM and 81.8GB virtual. Note that it is using up close to half of the swap space, even though the JVM only needs a subset of the physical memory. So what is causing the swapping, and what should I do about it? I can add more memory to the VMs if I need to, but how much? And how much should I allocate to JVM v. leave available for the OS? I could attach a screen shot of our Solr console and the top output if the listserv allows attachments. Any ideas? Thanks! Darrell Burgan [Description: Infor]<http://www.infor.com/> Darrell Burgan | Chief Architect, PeopleAnswers office: 214 445 2172 | mobile: 214 564 4450 | fax: 972 692 5386 | darrell.bur...@infor.com<mailto:darrell.bur...@infor.com> | http://www.infor.com CONFIDENTIALITY NOTE: This email (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, be aware that any disclosure, copying, distribution, or use of the information contained herein is prohibited. If you have received this message in error, please notify the sender by replying to this message and then delete this message in its entirety. Thank you for your cooperation.
