re are any other way to
>> reduce to memory requirement/optimize the performance.
>>
>>
>> Regards,
>>
>> Maulin
>>
>> -Original Message-
>> From: Shawn Heisey
>> Sent: 14 May 2019 01:04
>> To: solr-user@lucene.apach
> memory requirement/optimize the performance.
>
>
> Regards,
>
> Maulin
>
> -----Original Message-
> From: Shawn Heisey
> Sent: 14 May 2019 01:04
> To: solr-user@lucene.apache.org
> Subject: Re: Solr node goes into recovery mode
>
> On 5/13/2019 8:26 AM
eries. Please let me know your
> thoughts on it. Please also suggest if there are any other way to reduce to
> memory requirement/optimize the performance.
>
>
> Regards,
>
> Maulin
>
> -----Original Message-
> From: Shawn Heisey
> Sent: 14 May 2019 01:04
> To
Heisey
Sent: 14 May 2019 01:04
To: solr-user@lucene.apache.org
Subject: Re: Solr node goes into recovery mode
On 5/13/2019 8:26 AM, Maulin Rathod wrote:
> Recently we are observing issue where solr node (any random node)
> automatically goes into recovery mode and stops responding.
Do you
On 5/13/2019 8:26 AM, Maulin Rathod wrote:
Recently we are observing issue where solr node (any random node) automatically
goes into recovery mode and stops responding.
Do you KNOW that these Solr instances actually need a 60GB heap? That's
a HUGE heap. When a full GC happens on a heap that
There are a number of timeouts that can trip this, the ZK timeout is only one.
For instance, when a leader sends an update to a follower, if that times out
the leader may put the follower into “Leader Iniated Recovery” (LIR).
60G heaps are, by and large, not recommended for this very reason. Co
Hi,
We are using solr 6.1 version with 2 shards. Each shard have 1 replica set-up.
i.e. We have total 4 server nodes (each node is assigned 60 gb of RAM).
Recently we are observing issue where solr node (any random node) automatically
goes into recovery mode and stops responding.
We have enoug
