You need to restart your JVM anytime you hit an OOM exception, the state of the JVM is nondeterministic once you hit this. There is a JVM flag to automatically restart on OOM for this exact reason.
On Tue, May 3, 2022, 4:49 PM matthew sporleder <msporle...@gmail.com> wrote: > In my experience solr handles that stuff pretty well but I do, > occasionally, remember seeing lost file handles and weirdness after an OOM. > > On Tue, May 3, 2022 at 7:01 PM Vincenzo D'Amore <v.dam...@gmail.com> > wrote: > > > Hi all, > > > > I'm tuning a solrcloud 5.4.1 deployment (3 nodes, 12 cores each, 18GB > ram) > > that is experiencing frequent OutOfMemoryError (20 a day in total) > > exceptions during the execution of a group query. > > > > Looking at query group.limit=1 but the rows range between 1000 and 10000. > > I'm analyzing the solr query, and I've added a few JVM parameters to dump > > the active threads and the allocated memory to better analyze the OOM. > > But I was curious to ask in your experience how I should be preoccupied > by > > the OOM(s). > > In other words, I'm working to remove them ASAP, but when an OOM happens > > the Solr behaviour is completely compromised or Solr returns seamlessly > to > > work normally? > > > > Best regards, > > Vincenzo > > > > > > > > -- > > Vincenzo D'Amore > > >
