Hi Shawn, Thank you for looking into this. I have updated the jira with further investigation https://issues.apache.org/jira/browse/SOLR-17018. Please take a look and let me know what you all think.
On Mon, Oct 9, 2023 at 2:22 PM Shawn Heisey <apa...@elyograg.org.invalid> wrote: > On 10/8/23 18:24, rajani m wrote: > > I have filed a Jira SOLR-17018 > > <https://issues.apache.org/jira/browse/SOLR-17018> explaining the issue > and > > think it is just a certain type of queries causing the issue and not any > > bug, but still looking into it to see if anything else. > > You need to find out what resource was actually exhausted. It is not > always memory. Solr 9.1.1 may not always log the reason for the OOME, > and the gist you shared does not include the OutOfMemoryError exception. > > Solr 9.2.0 and later will always log the reason in a crash log. Before > doing ANYTHING, you must know which resource was exhausted, or you could > be chasing the wrong problem. > > Once you determine which resource was exhausted, there are exactly two > ways to deal with it: > > * Increase the available amount of the exhausted resource. > * Change the config or the requests you are sending so Solr uses less of > that resource. > > The second option is not always possible, and whether you can do the > first option depends on the hardware. > > Thanks, > Shawn > >
