k Erickson
> Sent: Tuesday, July 21, 2020 6:36 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Replica goes into recovery mode in Solr 6.1.0
>
> The recovery is probably _caused_ by the node not responding to the update
> request due to a timeout. The JIRA you reference is un
r-user@lucene.apache.org
Subject: Re: Replica goes into recovery mode in Solr 6.1.0
The recovery is probably _caused_ by the node not responding to the update
request due to a timeout. The JIRA you reference is unrelated I’d guess.
What kind of documents are you indexing? I have seen situations wher
Upgrade to 6.6.2. That will be compatible, but will fix several bugs that were
discovered during the 6.x releases.
If the problem happens after that, ask again. It might, we’ve had some issues
with 6.6.2, but upgrade first.
wunder
Walter Underwood
wun...@wunderwood.org
The recovery is probably _caused_ by the node not responding to the update
request due to a timeout. The JIRA you reference is unrelated I’d guess.
What kind of documents are you indexing? I have seen situations where massive
documents take so long that the request times out and starts this
Walter Underwood
Sent: Friday, July 10, 2020 11:15 PM
To: solr-user@lucene.apache.org
Subject: Re: Replica goes into recovery mode in Solr 6.1.0
Sorting and faceting takes a lot of memory. From your charts, I would try
a 31 GB heap. That would make GC faster. 680 ms is very long for a GC
and can ca
s] o.a.s.c.ZkController Put replica
> core=products coreNodeName=core_node3 on 11.200.212.305:8983_solr into
> leader-initiated recovery.
>
> So the node in question isn't responding quickly enough to http requests
> and gets put into recovery. The log for the recovering node starts too
> late
cause?
Regards,
Vishal Patel
From: Ere Maijala
Sent: Friday, July 10, 2020 4:27 PM
To: solr-user@lucene.apache.org
Subject: Re: Replica goes into recovery mode in Solr 6.1.0
vishal patel kirjoitti 10.7.2020 klo 12.45:
> Thanks for your input.
>
> Walter already said that setting sof
> ____
> From: Ere Maijala
> Sent: Friday, July 10, 2020 2:10 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Replica goes into recovery mode in Solr 6.1.0
>
> Walter already said that setting soft commit max time to 100 ms is a
> recipe
d/1y0fC_n5u3MBMQbXrvxtqaD8vBBXDLR6I/view>
drive.google.com
Regards,
Vishal Patel
From: Ere Maijala
Sent: Friday, July 10, 2020 2:10 PM
To: solr-user@lucene.apache.org
Subject: Re: Replica goes into recovery mode in Solr 6.1.0
Walter already said that setting soft commit max
recovery.
>
> Regards,
> Vishal Patel
>
> From: Walter Underwood
> Sent: Friday, July 10, 2020 3:03 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Replica goes into recovery mode in Solr 6.1.0
>
> Those are extremely large
o: solr-user@lucene.apache.org
Subject: Re: Replica goes into recovery mode in Solr 6.1.0
Those are extremely large JVMs. Unless you have proven that you MUST
have 55 GB of heap, use a smaller heap.
I’ve been running Solr for a dozen years and I’ve never needed a heap
larger than 8 GB.
Also, there is usu
gt;>> 55GB of one Solr JVM.
>
> Regards,
> Vishal Patel
>
> Sent from Outlook<http://aka.ms/weboutlook>
>
> From: Walter Underwood
> Sent: Wednesday, July 8, 2020 8:45 PM
> To: solr-user@lucene.apache.org
> Subject:
one Solr JVM.
Regards,
Vishal Patel
Sent from Outlook<http://aka.ms/weboutlook>
From: Walter Underwood
Sent: Wednesday, July 8, 2020 8:45 PM
To: solr-user@lucene.apache.org
Subject: Re: Replica goes into recovery mode in Solr 6.1.0
I don’t understand what
?
>
> "-Dsolr.autoSoftCommit.maxTime=100” is way too short (100 ms).
>>> Our requirement is NRT so we keep the less time
>
> Regards,
> Vishal Patel
> ________
> From: Walter Underwood
> Sent: Tuesday, July 7, 2020 8:15 PM
> To: s
8, 2020 4:23 PM
To: solr-user@lucene.apache.org
Subject: Re: Replica goes into recovery mode in Solr 6.1.0
Hi,
How do you show this? Command for this resume?
*Our collections details are below:
Collection Shard1 Shard1 Replica Shard2 Shard2 Replica
Number of Documents Size(GB
Hi,
How do you show this? Command for this resume?
*Our collections details are below:
Collection Shard1 Shard1 Replica Shard2 Shard2 Replica
Number of Documents Size(GB)Number of Documents Size(GB)
Number of Documents Size(GB)Number of Documents
s way too short (100 ms).
>> Our requirement is NRT so we keep the less time
Regards,
Vishal Patel
From: Walter Underwood
Sent: Tuesday, July 7, 2020 8:15 PM
To: solr-user@lucene.apache.org
Subject: Re: Replica goes into recovery mode in Solr 6.1.0
This is
This isn’t a support list, so nobody looks at issues. We do try to help.
It looks like you have 1 TB of index on a system with 320 GB of RAM.
I don’t know what "Shard1 Allocated memory” is, but maybe half of
that RAM is used by JVMs or some other process, I guess. Are you
running multiple huge
Any one is looking my issue? Please guide me.
Regards,
Vishal Patel
From: vishal patel
Sent: Monday, July 6, 2020 7:11 PM
To: solr-user@lucene.apache.org
Subject: Replica goes into recovery mode in Solr 6.1.0
I am using Solr version 6.1.0, Java 8 version and
19 matches
Mail list logo
