Daniel Cukier [danic...@gmail.com] wrote: > The servers have around 4M documents and receive a constant > flow of queries. When the solr server starts, it works fine. But after some > time running, it starts to take longer respond to queries, and the server > I/O goes crazy to 100%. Look at the New Relic graphic:
Two possible explanations: 1) You update the indexes and you commit too frequently, causing the Solrs to have overlapping upstarting searchers, each requiring IO. If you have many warmup queries, this excerberates the issue. 2) Your Xms and Xmx are different, with your Xmx being high, relative to physical memory on the server. At the beginning the allocated memory for the JVM will be low, leaving a lot of memory for disk caching. As you issue requests, heap memory allocation grows, leaving less memory for disk cache. 3) You have very little memory free for disk cache and a fairly large swap space. For some setups that will cause the OS to swap all the time. - Toke Eskildsen
