On 10/7/22 20:15, Satya Nand wrote:
After sometime mapped total capacity reached to 100 GB(probably after some
commit). Young GC count doubled and server threw out of memory error.
Any insights? What we can check to avoid this?
Did you actually see the OutOfMemoryError exception? The exception will
include a note to say what resource was depleted. It is frequently NOT
memory. We need to chase the right resource.
I have been working on something in SOLR-8803 that will ensure we always
can see the cause of an OOME. The patch cannot be applied to Solr 8.x,
it has to go into 9.x. That's because the new option was added to Java
8u92 and with Solr 8.x we cannot guarantee that the user has a new
enough Java version. For Solr 9.x we can, because it requires Java 11.
https://issues.apache.org/jira/browse/SOLR-8803
The parts of the patch that affect the bin directory can be applied to a
binary download to get the new OOME behavior.
Thanks,
Shawn
