> cores with the same name) because someone did a backup of an existing one ...
>
> Thank you for your support!
> - Torsten
>
> -Ursprüngliche Nachricht-
> Von: Erick Erickson
> Gesendet: Freitag, 6. März 2020 16:22
> An: solr-user@lucene.apache.org
>
Nachricht-
Von: Erick Erickson
Gesendet: Freitag, 6. März 2020 16:22
An: solr-user@lucene.apache.org
Betreff: Re: Problem with Solr 7.7.2 after OOM
Is it still giving you OOMs? That was the original problem statement. If not,
then you need to look at your Solr logs to see what error is
; Gesendet: Freitag, 6. März 2020 09:33
> An: solr-user@lucene.apache.org
> Betreff: AW: Problem with Solr 7.7.2 after OOM
>
> I set the heap to 8g but this doesn't have any effect and the problem is
> still the same.
>
> ~# ps -eaf | grep solr
> solr
@lucene.apache.org
Betreff: AW: Problem with Solr 7.7.2 after OOM
I set the heap to 8g but this doesn't have any effect and the problem is still
the same.
~# ps -eaf | grep solr
solr 3176 1 0 08:50 ?00:00:00 /lib/systemd/systemd --user
solr 3177 3176 0
26388 62793615034128 796 764324
15488956
Swap:969960 0 969960
~#
Torsten
-Ursprüngliche Nachricht-
Von: Jörn Franke
Gesendet: Donnerstag, 5. März 2020 17:31
An: solr-user@lucene.apache.org
Betreff: Re: Problem with Solr 7.7.2 after OOM
Just keep in mind that the total memory should be much more than the heap to
leverage Solr file caches. If you have 8 GB heap probably at least 16 gb total
memory make sense to be available on the machine .
> Am 05.03.2020 um 16:58 schrieb Walter Underwood :
>
>
>>
>> On Mar 5, 2020, at 4:29
> On Mar 5, 2020, at 4:29 AM, Bunde Torsten wrote:
>
> -Xms512m -Xmx512m
Your heap is too small. Set this to -Xms8g -Xmx8g
In solr.in.sh, that looks like this:
SOLR_HEAP=8g
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
Hello @all,
I've got a problem with Solr (version 7.7.2) since some days.
On March, 4th I got an OOM and the log file just says the following:
Running OOM killer script for process 12351 for Solr on port 8983
Killed process 12351
So I started the service again and the service is running fine. B
