On 5/25/2019 6:43 AM, Saurabh Sharma wrote:
Hi,
Link to image https://ibb.co/8g6gXwr
That screenshot is not sorted the way that was mentioned on the wiki
page - by the RES memory column. I do see several other Java processes
besides Solr. There might be other high-memory use processes that are
not visible because of the sort order.
It doesn't look like memory is a big problem here -- there is still 5GB
free at the OS level, disk cache usage looks OK, and iowait CPU
percentage seems to be zero.
Based on what I can see, I'm betting you're just throwing more load at
this machine than it can handle currently. It might be a matter of the
query rate, or it might be that when this happens, Solr is handling
particularly resource-intensive queries.
It does look like you have memory to spare, so you could try increasing
Solr's heap from 12GB to 14GB or 16GB, see if that helps at all. If it
does, it means the heap was smaller than it needed to be to handle the
kinds of queries Solr was doing. I'm guessing here.
Thanks,
Shawn
