On 8/13/2019 6:19 AM, Kojo wrote:
-------------- tail -f node1/logs/solr_oom_killer-8983-2019-08-11_22_57_56.log Running OOM killer script for process 38788 for Solr on port 8983 Killed process 38788 --------------
Based on what I can see, a 6GB heap is not big enough for the setup you've got. There are two ways to deal with an OOME problem. 1) Increase the resource that was depleted. 2) Change the configuration so the program needs less of that resource.
https://cwiki.apache.org/confluence/display/solr/SolrPerformanceProblems#SolrPerformanceProblems-JavaHeap
tail -50 node1/logs/archived/solr_gc.log.4.current
To be useful, we will need the entire GC log, not a 50 line subset. In the subset, I can see that there was a full GC that did absolutely nothing -- no memory was freed. This is evidence that your heap is too small. You will need to use a file shariog site and provide a URL for the entire GC log - email attachments rarely make it to the list. The bigger the log is, the better idea we can get about what heap size you need.
Thanks, Shawn
