On 12/13/21 8:53 AM, Scott wrote:
I guess my questions are:
- Why does Solr use more than 16g ?
- Why isn't swapped memory released ?
Solr is a Java program, and it is Java that manages the memory. If the
process is going significantly beyond the 16GB max heap that has been
configured, and sw
er 13, 2021 12:24 PM
> To: users@solr.apache.org
> Subject: Re: Solr Cloud Node re-join issue
>
> The heap size limits the Java heap. Java uses memory that is not in the heap
> — bytecodes, compiled code, stack, threadlocal, mapped memory, etc.
>
> wunder
> Walter Underwoo
read all got started.
Thanks!
-Original Message-
From: Walter Underwood
Sent: Monday, December 13, 2021 12:24 PM
To: users@solr.apache.org
Subject: Re: Solr Cloud Node re-join issue
The heap size limits the Java heap. Java uses memory that is not in the heap —
bytecodes, compiled code
00% and the box will crash.
>
> I guess my questions are:
> - Why does Solr use more than 16g ?
> - Why isn't swapped memory released ?
>
> Thanks!
> Scott
>
> -Original Message-----
> From: Shawn Heisey
> Sent: Monday, December 13, 2021 12:41 AM
> To:
released ?
Thanks!
Scott
-Original Message-
From: Shawn Heisey
Sent: Monday, December 13, 2021 12:41 AM
To: users@solr.apache.org
Subject: Re: Solr Cloud Node re-join issue
On 12/12/2021 4:40 PM, Scott wrote:
> However, top still shows Solr using more than 16g . It started at 17g
> and has
On 12/12/2021 4:40 PM, Scott wrote:
However, top still shows Solr using more than 16g . It started at 17g and has
been steadily growing, now it's at 23g and soon it will go into swap
PID USERNAMETHR PRI NICE SIZE RES SWAP STATEC TIME
WCPU COMMAND
57116 solr
sey
Sent: Saturday, December 11, 2021 1:30 PM
To: users@solr.apache.org
Subject: Re: Solr Cloud Node re-join issue
On 12/11/2021 8:39 AM, Scott wrote:
> Thanks Shawn. Most people I talked to sort of acknowledged that restarting
> SOLR every month or so is a given, but your comments are enc
On 12/11/2021 8:39 AM, Scott wrote:
Thanks Shawn. Most people I talked to sort of acknowledged that restarting SOLR
every month or so is a given, but your comments are encouraging.
These nodes have 32Gb of ram:
real memory = 34359738368 (32768 MB)
avail memory = 33370628096 (31824 MB)
and he
onfig
SOLR_JAVA_MEM="-Xms14512m -Xmx16512m"
I thought I'd keep it at half of available RAM but it still goes into swap...
Thank you for your help
-Original Message-
From: Shawn Heisey
Sent: Saturday, December 11, 2021 1:25 AM
To: users@solr.apache.org
Subject: Re: Solr Clou
On 12/10/2021 12:38 PM, Scott wrote:
Having a bit of weird issue.
We run a 4 node Solr Cloud , version 8.6.2 and for the most part it's been
going quite well for more than 2 years now. We have to restart them
occasionally to free up ram but I guess that's normal.
If you have to restart becaus
I managed to get it to start replicating the missing nodes, manually, using:
curl
"http://192.168.1.4:8983/solr/admin/collections?action=ADDREPLICA&collection=mycollection&shard=shard10&node=192.168.1.11:8983_solr";
Is it normal to have to tell it manually which replicas to host after such a
cr
11 matches
Mail list logo
