lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Midas A <test.mi...@gmail.com>
Subject Re: not able to optimize
Date Tue, 04 Jun 2019 09:37:14 GMT
400GB index is good ?
Are we should shard it .?

When we should start caring about inex size .?

On Tue, Jun 4, 2019 at 3:04 PM Midas A <test.midas@gmail.com> wrote:

> So we should not optimize our index ?
>
> On Tue, Jun 4, 2019 at 2:37 PM Toke Eskildsen <toes@kb.dk> wrote:
>
>> On Tue, 2019-06-04 at 11:48 +0530, Midas A wrote:
>> >  Index size is 400GB. we used master slave architecture .
>> >
>> > commit is taking time while not able to perform optimize .
>>
>> Why do you want to optimize in the first place? What are you hoping to
>> achieve?
>>
>> There should be an error message in your Solr log from the failed
>> optimize, so see if you can find that. At least for some Solr versions,
>> optimize can be quite memory hungry so a very quick guess is that you
>> have hit an OutOfMemory. Not enough disk space is also a guess: Make
>> sure you have 2*index size free space before optimizing as worst case
>> for storage usage during optimize is a total of 3*index size.
>>
>> - Toke Eskildsen, Royal Danish Library
>>
>>
>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message