Emir, after digging deeper into the logs (using new relic/solr admin) during the outage, it looks like a combination of query load and indexing process triggered it. Based on the earlier pattern, memory would tend to increase at a steady pace, but then surge all of a sudden, triggering OOM. After I scaled down the heap size as per Walter's suggestion, the memory seemed to have been holding up. But there's a possibility the lower heap size might have restricted the GC to utilize higher CPU. The cache size has been scaled down, I'm hoping it's no longer adding an overhead after every commit.
I've facet.limit=-1 configured for few search types, but facet.mincount is always set as 1. Didn't know that's detrimental to doc values. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
