Ah gotcha. Well you can just keep upping it gig by gig until it doesn’t happen anymore, but the man hours/salary spent trying to track down the issue very quickly out cost the money for the memory
> On Jun 25, 2021, at 1:08 PM, Dominique Bejean <dominique.bej...@eolya.fr> > wrote: > > Hum, maybe it is an acceptable way of setting the JVM heap if you really > have a lot of memory and you are using G1 GC. > But sorry, my customers don't agree with "disk and memory are cheap" :) > Furthermore, if you can save some money on each of your servers, maybe you > can rent one more server and so increase available CPU, disk space and disk > I/0. > > Dominique > > > >> Le ven. 25 juin 2021 à 18:56, Dave <hastings.recurs...@gmail.com> a écrit : >> >> Because memory is cheap, I’m assuming the server has plenty more after, >> and more the better for the jvm in my experience. It’s just a default >> value I go for when this occurs, and then never after and no oom error ever >> again >> >>> On Jun 25, 2021, at 12:47 PM, Dominique Bejean < >> dominique.bej...@eolya.fr> wrote: >>> >>> Hi Dave, >>> >>> I agree with not allocating more than 31 GB for Xms/Xmx as it is the >> upper >>> limit in order for the JVM to use compressed oops ( >>> >> https://blog.codecentric.de/en/2014/02/35gb-heap-less-32gb-java-jvm-memory-oddities/ >> ), >>> but why directly 31 Gb without more Solr usage analysis ? >>> >>> Dominique >>> >>> >>> >>>> Le ven. 25 juin 2021 à 16:25, Dave <hastings.recurs...@gmail.com> a >> écrit : >>>> >>>> Another thing I would keep in mind is running your xms and xmx at the >> same >>>> memory size. Ideally the machine it’s on has a lot of memory, so if >> both >>>> are set to 31gb, and the os still has enough memory to read your index, >> is >>>> nearly ideal. >>>> >>>>>> On Jun 25, 2021, at 8:36 AM, Rafał Kuć <r....@solr.pl> wrote: >>>>> >>>>> Hello Paul, >>>>> >>>>> The error that you are seeing tells you that your Solr instance didn't >>>> have enough memory to run certain operation - for example indexing or >>>> querying. Have a look at this page of the documentation: >>>> >> https://solr.apache.org/guide/6_6/jvm-settings.html#JVMSettings-ChoosingMemoryHeapSettings >>>> < >>>> >> https://solr.apache.org/guide/6_6/jvm-settings.html#JVMSettings-ChoosingMemoryHeapSettings >>> >>>> - though it is for version 6.6 it is valuable for Solr 5.2.1 as well. >> You >>>> may just not have enough memory given to the JVM. I would start with >> that. >>>>> >>>>> Check your Solr logs to find out the problematic part and when it >>>> happens. If that happens during the query time you will usually find >> longer >>>> than usual running queries. That's a good place to start. >>>>> >>>>> >>>>> --- >>>>> Regards, >>>>> Rafał Kuć >>>>> >>>>> >>>>> >>>>> >>>>>> On 25 Jun 2021, at 10:52, Paul, Lulu <lulu.p...@bl.uk> wrote: >>>>>> >>>>>> Hi team, >>>>>> >>>>>> We are running SOLR 5.2.1 version and this is the error we receive on >>>> our LIVE instance. I am relatively new to the project and still learning >>>> about SOLR. >>>>>> >>>>>> org.apache.solr.common.SolrException; null:java.lang.RuntimeException: >>>> java.lang.OutOfMemoryError: Java heap space >>>>>> >>>>>> Please can you suggest what should be checked and a possible >> resolution >>>> to this problem ? >>>>>> >>>>>> Below is the into from SOLR UI Dashboard on system space : >>>>>> >>>>>> >>>>>> >>>>>> Much appreciate your advice >>>>>> Thank you, best wishes Lulu >>>>>> >>>>>> >>>>>> >>>>>> >>>> >> ****************************************************************************************************************** >>>>>> Experience the British Library online at www.bl.uk <http://www.bl.uk/ >>> >>>>>> The British Library’s latest Annual Report and Accounts : >>>> www.bl.uk/aboutus/annrep/index.html < >>>> http://www.bl.uk/aboutus/annrep/index.html> >>>>>> Help the British Library conserve the world's knowledge. Adopt a Book. >>>> www.bl.uk/adoptabook <http://www.bl.uk/adoptabook> >>>>>> The Library's St Pancras site is WiFi - enabled >>>>>> >>>> >> ***************************************************************************************************************** >>>>>> The information contained in this e-mail is confidential and may be >>>> legally privileged. It is intended for the addressee(s) only. If you are >>>> not the intended recipient, please delete this e-mail and notify the >>>> postmas...@bl.uk <mailto:postmas...@bl.uk> : The contents of this >> e-mail >>>> must not be disclosed or copied without the sender's consent. >>>>>> The statements and opinions expressed in this message are those of the >>>> author and do not necessarily reflect those of the British Library. The >>>> British Library does not take any responsibility for the views of the >>>> author. >>>>>> >>>> >> ***************************************************************************************************************** >>>>>> Think before you print >>>>> >>>> >>
