different.
>
> --Jamie
>
> -Original Message-
> From: Dave
> Sent: Friday, June 25, 2021 1:18 PM
> To: users@solr.apache.org
> Subject: Re: SolrException : java.lang.OutOfMemoryError: Java heap space
>
> CAUTION: This email originated from outside of
PM
To: users@solr.apache.org
Subject: Re: SolrException : java.lang.OutOfMemoryError: Java heap space
CAUTION: This email originated from outside of Biospatial. Do not click links
or open attachments unless you recognize the sender and know the content is
safe.
Ah gotcha. Well you can just
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
> wrote:
>
> Hum, maybe it is an acceptable way
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 i
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
> wrote:
>
> Hi D
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
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ć 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-ChoosingMemoryHeapSet
