On 2/27/2017 4:57 PM, Rick Leir wrote: > We get an OOM after stopping then starting Solr (with a tiny index). Is > there something I could check quickly before I break out the Eclipse > debugger? Maybe Marple could tell me about problems in the index?
There are exactly two ways of dealing with OOME, assuming that there's not a bug in the software. 1) Increase the heap size. 2) Figure out why the program needs so much memory and change the configuration to reduce the amount required. Action number 2 may prove to be difficult. There are no other possible solutions. We are not aware of any memory leaks in Solr, Lucene, or any of the other dependencies. There could be a memory leak, but if there is, it has not yet been discovered. It is likely that even if you have a stacktrace showing the OOME error that the place where the OOME occurred will have absolutely nothing to do with the part of the system that is requiring a lot of memory. You can share this error if you want, but I will warn you that it is probably not useful information. Here's some generic info about what causes high heap requirements with Solr. It is not an exhaustive list: https://wiki.apache.org/solr/SolrPerformanceProblems#Java_Heap Further down on the page is a section about *reducing* the amount of heap required. Thanks, Shawn
