On 10/25/2016 8:03 PM, Susheel Kumar wrote: > Agree, Pushkar. I had docValues for sorting / faceting fields from > begining (since I setup Solr 6.0). So good on that side. I am going to > analyze the queries to find any potential issue. Two questions which I am > puzzling with > > a) Should the below JVM parameter be included for Prod to get heap dump > > "-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/path/to/the/dump"
A heap dump can take a very long time to complete, and there may not be enough memory in the machine to start another instance of Solr until the first one has finished the heap dump. Also, I do not know whether Java would release the listening port before the heap dump finishes. If not, then a new instance would not be able to start immediately. If a different heap dump file is created each time, that might lead to problems with disk space after repeated dumps. I don't know how the option works. > b) Currently OOM script just kills the Solr instance. Shouldn't it be > enhanced to wait and restart Solr instance As long as there is a problem causing OOMs, it seems rather pointless to start Solr right back up, as another OOM is likely. The safest thing to do is kill Solr (since its operation would be unpredictable after OOM) and let the admin sort the problem out. Thanks, Shawn
